[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-2170) GWT example in 2.0.0 CR3 does not work
Shane Bryzak (JIRA)
jira-events at lists.jboss.org
Tue Oct 30 00:03:01 EDT 2007
[ http://jira.jboss.com/jira/browse/JBSEAM-2170?page=all ]
Shane Bryzak closed JBSEAM-2170.
--------------------------------
Resolution: Cannot Reproduce Bug
I just tested the GWT example and I cannot reproduce this exception.
> GWT example in 2.0.0 CR3 does not work
> --------------------------------------
>
> Key: JBSEAM-2170
> URL: http://jira.jboss.com/jira/browse/JBSEAM-2170
> Project: JBoss Seam
> Issue Type: Bug
> Components: Remoting
> Affects Versions: 2.0.0.CR3
> Environment: JBoss 4.2.1 / Seam 2.0.0 CR3/ GWT 1.4.60
> Reporter: Kishore R
> Assigned To: Shane Bryzak
>
> I compiled the GWT example in the 2.0 CR3 release with GWT 1.4.60 and deployed it. I get the following error on the server
> --------------------------------------------------------------------------------------------------------
> java.lang.IllegalStateException: No active event context
> at org.jboss.seam.core.Manager.instance(Manager.java:248)
> at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHtt
> pServletRequest.java:55)
> at org.jboss.seam.web.ContextFilter.doFilter(ContextFilter.java:37)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
> icationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
> ilterChain.java:206)
> at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi
> lter.java:96)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
> icationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
> ilterChain.java:206)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
> alve.java:230)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
> alve.java:175)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit
> yAssociationValve.java:179)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv
> e.java:84)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
> ava:128)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
> ava:104)
> at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedC
> onnectionValve.java:157)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
> ve.java:109)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
> a:241)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
> :844)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
> ss(Http11Protocol.java:580)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:44
> 7)
> at java.lang.Thread.run(Thread.java:595)
> 14:51:18,312 ERROR [[Seam Resource Servlet]] Servlet.service() for servlet Seam
> Resource Servlet threw exception
> java.lang.IllegalStateException: No active event context
> at org.jboss.seam.core.Manager.instance(Manager.java:248)
> at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHtt
> pServletRequest.java:55)
> at org.jboss.seam.web.ContextFilter.doFilter(ContextFilter.java:37)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
> icationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
> ilterChain.java:206)
> at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi
> lter.java:96)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
> icationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
> ilterChain.java:206)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
> alve.java:230)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
> alve.java:175)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit
> yAssociationValve.java:179)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv
> e.java:84)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
> ava:128)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
> ava:104)
> at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedC
> onnectionValve.java:157)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
> ve.java:109)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
> a:241)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
> :844)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
> ss(Http11Protocol.java:580)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:44
> 7)
> at java.lang.Thread.run(Thread.java:595)
> ----------------------------------------------------------------------------------------------------------
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues
mailing list