3 Replies Latest reply on Oct 2, 2006 10:57 PM by billbruyn

    remoting helloworld on tomcat

    billbruyn
    billbruyn Oct 2, 2006 10:17 AM

      Should I be able to deploy the remoting helloworld example to a standalone tomcat? A few properties were left out of the build script so that deploy.tomcat didn't work like it did with the other examples I've tried. Fixed that up and got it to deploy, but now I get the following on execution. Did I leave something out of the build, or am I barking up the wrong tree here?

      ERROR 02-10 07:03:58,589 (Log4JLogger.java:error:119) -Error during remote request
org.jboss.seam.InstantiationException: Could not instantiate Seam component: helloAction
 at org.jboss.seam.Component.newInstance(Component.java:735)
 at org.jboss.seam.Component.newInstance(Component.java:1308)
 at org.jboss.seam.Component.getInstance(Component.java:1263)
 at org.jboss.seam.Component.getInstance(Component.java:1246)
 at org.jboss.seam.remoting.Call.execute(Call.java:101)
 at org.jboss.seam.remoting.ExecutionHandler.handle(ExecutionHandler.java:92)
 at org.jboss.seam.remoting.SeamRemotingServlet.doPost(SeamRemotingServlet.java:56)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
 at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
 at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
 at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
 at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
 at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
 at java.lang.Thread.run(Thread.java:595)
Caused by: javax.naming.NamingException: Local server is not initialized
 at org.jnp.interfaces.LocalOnlyContextFactory.getInitialContext(LocalOnlyContextFactory.java:45)
 at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
 at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
 at javax.naming.InitialContext.init(InitialContext.java:223)
 at javax.naming.InitialContext.<init>(InitialContext.java:197)
 at org.jboss.seam.util.Naming.getInitialContext(Naming.java:26)
 at org.jboss.seam.util.Naming.getInitialContext(Naming.java:37)
 at org.jboss.seam.Component.instantiate(Component.java:774)
 at org.jboss.seam.Component.newInstance(Component.java:731)
 ... 22 more


      • 7166 Views
      • Tags: