[JBoss Seam] - Remoting
by KoniKoni
| cl=org.jboss.mx.loading.HeirarchicalLoaderRepository3$CacheClassLoader@921158{ url=null ,addedOrder=0}
| 2006-12-19 22:41:06,757 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@108c98, cl=org.jboss.mx.loading.HeirarchicalLoaderRepository3$CacheClassLoader@1b0c258{ url=null ,addedOrder=0}
| 2006-12-19 22:41:06,757 ERROR [org.jboss.seam.remoting.ExecutionHandler] Error during remote request
| org.dom4j.DocumentException: Error on line -1 of document : Premature end of file. Nested exception: Premature end of file.
| at org.dom4j.io.SAXReader.read(SAXReader.java:482)
| at org.dom4j.io.SAXReader.read(SAXReader.java:343)
| at org.jboss.seam.remoting.ExecutionHandler.handle(ExecutionHandler.java:68)
| at org.jboss.seam.remoting.SeamRemotingServlet.doPost(SeamRemotingServlet.java:77)
| at org.jboss.seam.remoting.SeamRemotingServlet.doGet(SeamRemotingServlet.java:62)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:46)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| 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.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| 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.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:595)
| Nested exception:
| org.xml.sax.SAXParseException: Premature end of file.
| at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
| at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
| at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
| at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
| at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
| at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
| at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
| at org.dom4j.io.SAXReader.read(SAXReader.java:465)
| at org.dom4j.io.SAXReader.read(SAXReader.java:343)
| at org.jboss.seam.remoting.ExecutionHandler.handle(ExecutionHandler.java:68)
| at org.jboss.seam.remoting.SeamRemotingServlet.doPost(SeamRemotingServlet.java:77)
| at org.jboss.seam.remoting.SeamRemotingServlet.doGet(SeamRemotingServlet.java:62)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:46)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| 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.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| 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.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:595)
| 2006-12-19 22:41:06,767 DEBUG [org.jboss.seam.contexts.Lifecycle] After request, destroying contexts
| 2006-12-19 22:41:06,787 DEBUG [org.jboss.seam.remoting.ExecutionHandler] ended request
| 2006-12-19 22:41:06,787 ERROR [org.jboss.seam.servlet.SeamServletFilter] Error
| java.lang.IllegalStateException: No active event context
| at org.jboss.seam.core.Manager.instance(Manager.java:249)
| at org.jboss.seam.contexts.Lifecycle.flushAndDestroyContexts(Lifecycle.java:354)
| at org.jboss.seam.contexts.Lifecycle.endRequest(Lifecycle.java:272)
| at org.jboss.seam.remoting.ExecutionHandler.handle(ExecutionHandler.java:101)
| at org.jboss.seam.remoting.SeamRemotingServlet.doPost(SeamRemotingServlet.java:77)
| at org.jboss.seam.remoting.SeamRemotingServlet.doGet(SeamRemotingServlet.java:62)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:46)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| 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.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| 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.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:595)
| 2006-12-19 22:41:06,807 DEBUG [org.jboss.seam.util.Naming] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
This is the output from firefox console
Fehler: Kein Element gefunden (Error no element found)
Quelldatei: http://localhost:8080/laola/seam/remoting/execute
Zeile: 1, Spalte: 1
Quelltext:
^
My Code:
Seam.Component.getInstance("remoteaction").getBets(0,showSiteInfos);
This is the methode from session bean
public SiteHelper getBets(int id){}
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995130#3995130
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995130
19 years, 4 months
[JBoss Seam] - Re: Request for feedback
by gavin.king＠jboss.com
OK, so after much to and fro, I settled on the following:
anonymous wrote : <page view-id="/edit.jsp">
|
|
|
|
| <navigation from-action="#{home.load}">
|
| <render view-id="/404.jsp"/>
|
|
| <render view-id="/view.jsp">
|
|
|
|
| <begin-conversation/>
|
|
|
| <navigation from-action="#{home.update}">
| <redirect view-id="#{/view.jsp}">
| <end-conversation/>
|
|
|
|
|
Or, alternatively:
anonymous wrote : <page view-id="/edit.jsp">
|
|
|
|
| <navigation from-action="#{home.load}">
| <rule if-outcome="not-found">
| <render view-id="/404.jsp"/>
|
| <rule if-outcome="read-only">
| <render view-id="/view.jsp">
|
|
|
| <rule if-outcome="found">
| <begin-conversation/>
|
|
|
| <navigation from-action="#{home.update}">
| <redirect view-id="#{/view.jsp}">
| <end-conversation/>
|
|
|
|
|
Or even:
anonymous wrote : <page view-id="/edit.jsp">
|
|
|
|
| <navigation from-action="#{home.load}"
| evaluate="#{home.status}">
| <rule if-outcome="NOT_FOUND">
| <render view-id="/404.jsp"/>
|
| <rule if-outcome="READ_ONLY">
| <render view-id="/view.jsp">
|
|
|
| <rule if-outcome="FOUND">
| <begin-conversation/>
|
|
|
| <navigation from-action="#{home.update}">
| <redirect view-id="#{/view.jsp}">
| <end-conversation/>
|
|
|
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995127#3995127
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995127
19 years, 4 months
[JBoss Seam] - Think I found the problem
by chris.morrisette
Ok. I think I found the problem in the class:
org.jboss.seam.interceptors.RemoveInterceptor
The line (77):
getComponent().getScope().getContext().remove( getComponent().getName() );
Will remove a bean with the specified name from the conversation associated with the current thread.
The problem is, that the current thread is cleaning up timed out conversations not associated with the current thread. Since, getComponent().getScope().getContext().remove( getComponent().getName() ); removes objects from the current thread (instead of the timed out thread) you end up having objects removed from the current threads conversation by accident.
I was also able to watch this happen in the Seam.debug servlet. Starting two conversations a minute after each other with the same Components loaded, and the component would be removed from the conversation associated with the current thread, not the thread that is timing out.
Thoughts? Am I completely wrong?
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995123#3995123
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995123
19 years, 4 months