[JBoss Seam] - Re: Seam debug error
by h.cahyadi
Last night I upgrade to seam 1.2 Patch 1 and I get different error like this :
| 08:57:28,671 INFO [Lifecycle] starting up: org.jboss.seam.security.identity
| 08:57:28,750 ERROR [PhaseListenerManager] Exception in PhaseListener RENDER_RESP
| ONSE(6) beforePhase.
| java.lang.IllegalStateException: No active application scope
| at org.jboss.seam.core.Init.instance(Init.java:78)
| at org.jboss.seam.debug.jsf.SeamDebugPhaseListener.beforePhase(SeamDebug
| PhaseListener.java:38)
| at org.apache.myfaces.lifecycle.PhaseListenerManager.informPhaseListener
| sBefore(PhaseListenerManager.java:73)
| at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:
| 126)
| at javax.faces.webapp.FacesServlet.service(FacesServlet.java:140)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
| icationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
| ilterChain.java:173)
| at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.jav
| a:63)
| at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
| at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.jav
| a:49)
| at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57)
| at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.jav
| a:49)
| at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.jav
| a:53)
| at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:79)
| at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.jav
| a:49)
| at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
| icationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
| ilterChain.java:173)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi
| lter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
| icationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
| ilterChain.java:173)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
| alve.java:213)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
| alve.java:178)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit
| yAssociationValve.java:175)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv
| e.java:74)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
| ava:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
| ava:105)
| at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConne
| ctionValve.java:156)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
| ve.java:107)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
| a:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
| :869)
| at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.p
| rocessConnection(Http11BaseProtocol.java:664)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo
| int.java:527)
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWor
| kerThread.java:112)
| at java.lang.Thread.run(Thread.java:595)
|
I already enabled the debug in the web.xml, I also set debug parameter to true in the components.xml, I also added seam-debug.jar inside the lib directory inside the .war, is there something I missed? any suggestion?
Thanx and Regards,
-haric-
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025650#4025650
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025650
19Â years, 1Â month
[JBoss Seam] - Re: seam gen - which one?
by stu2
Oops! Let's try that again...
"gavin.king(a)jboss.com" wrote : anonymous wrote : is support for the WTP planned?
|
| This is a subject of debate between myself and Max.
I'm sure supporting the typical WTP project structures would make seam-gen and the build script substantially more complex, and generally be a pita for the already-busy dev team.
But this structure (web, java and ear projects for instance) is extremely common outside of seam projects. And trying to shoehorn current seam-gen's output into this structure is a bear - you're basically asking to spend a lot of time getting it to work again (unless you're a seam veteran). And after it works again, seam-gen's handy new-stuff tasks no longer put things in the "right" place.
I think the above represents an adoption barrier to seam. I've been using the current seam-gen produced structure, and it works fine. But when I later go back to my client and try to convince them to consider seam, having an only-seam-projects-look-like-this structure will make it a hard sell. Sounds silly given how fantastic seam is. But it's also true.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025645#4025645
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025645
19Â years, 1Â month