[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-406) debug.seam causes exception
by Albert Yu (JIRA)
[ http://jira.jboss.com/jira/browse/JBSEAM-406?page=comments#action_12348217 ]
Albert Yu commented on JBSEAM-406:
----------------------------------
I still get this error all time. It must be something that has not been fully fixed.
> debug.seam causes exception
> ---------------------------
>
> Key: JBSEAM-406
> URL: http://jira.jboss.com/jira/browse/JBSEAM-406
> Project: JBoss Seam
> Issue Type: Bug
> Components: Tools
> Affects Versions: 1.1.0.BETA1
> Environment: jboss 4.0.5CR1 with Seam CVS and RC9 of EJB3
> Reporter: jarkko Lietolahti
> Fix For: 1.1.0.BETA2
>
>
> Accessing http://localhost:8080/seamApp/debug.seam causes the following exception in log (and 404 on the brorwser).
> 150438 16:57:07,871 ERROR [PhaseListenerManager] Exception in PhaseListener RENDER_RESPONSE(6) beforePhase.
> javax.faces.el.PropertyNotFoundException: /file:/home/jarkko/seam-workspace/tear/src/tc3.ear/tc3Web.war/WEB-INF/lib/jboss-seam-debug.jar!/META-INF/debug.xhtml @63,90 rendered="#{empty org$jboss$seam$debug$contexts.conversationEntries}": Bean: org.jboss.seam.debug.Contexts$$EnhancerByCGLIB$$fb7d5aec, property: conversationEntries
> at com.sun.facelets.el.LegacyValueBinding.getValue(LegacyValueBinding.java:58)
> at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:1076)
> at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:231)
> at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:239)
> at org.jboss.seam.debug.jsf.SeamDebugPhaseListener.beforePhase(SeamDebugPhaseListener.java:50)
> at org.apache.myfaces.lifecycle.PhaseListenerManager.informPhaseListenersBefore(PhaseListenerManager.java:70)
> at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:373)
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:138)
> 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:45)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
> at org.jboss.seam.servlet.SeamRedirectFilter.doFilter(SeamRedirectFilter.java:33)
> 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.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432)
> 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:153)
> 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:619)
--
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
18 years, 1 month
[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-256) Entity-driven processes
by Tom Baeyens (JIRA)
[ http://jira.jboss.com/jira/browse/JBSEAM-256?page=comments#action_12348116 ]
Tom Baeyens commented on JBSEAM-256:
------------------------------------
Ah, now i remember. We had this discussion before. It all boiled down to wether you want special optimized support for the pattern where you have a process variable called "business key". The difference is that with process variables, it's stored in a separate table. So the query will be slightly different. Currently the datamodel sucks a bit in that respect so finding process instances based on variable values takes too many navigations. But that is a different issue. The real issue is whether it is worth to have 1 specially treated string-based user-defined variable that is part of the process instance table and which relates 1-1 with the process instance id.
One of the ideologies of the jBPM guys is that "hibernate should have better support for equals based on the PK" then, there would be no problem that needs fixing :-)
Also, I do not see yet what this business key should bring to the table in terms of features for a jBPM user. What use cases do you have in mind ?
> Entity-driven processes
> -----------------------
>
> Key: JBSEAM-256
> URL: http://jira.jboss.com/jira/browse/JBSEAM-256
> Project: JBoss Seam
> Issue Type: Feature Request
> Components: BPM
> Reporter: Gavin King
> Assigned To: Gavin King
>
> We need new functionality in jBPM to allow us to navigate to a process from an entity related to the process.
--
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
18 years, 1 month
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-551) Session scoped SFSB's cannot be destroyed at HTTP session timeout
by Ryan Dewell (JIRA)
Session scoped SFSB's cannot be destroyed at HTTP session timeout
-----------------------------------------------------------------
Key: JBSEAM-551
URL: http://jira.jboss.com/jira/browse/JBSEAM-551
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 1.1.0.CR2, 1.1.0.CR1
Environment: JBoss 4.0.5
Reporter: Ryan Dewell
Between 1.1 Beta1 and 1.1 CR1, an issue has been introduced where an EJBNoSuchObjectException / could not destroy component warning is thrown when session timeout occurs.
It appears to specifically effect components which are Session scoped SFSB's.
This can be reproduced by simply using the "issues" example that ships with Seam. The issues example has a session scoped SFSB component called "login".
Set the session timeout in web.xml to 1 minute and build the issues example. Navigate to seam-issues/login.jsf to activate the component.
Wait 1 minute and the exception / warning will be thrown in CR1 and CR2. No exception / warning will be thrown in Beta1 (or below).
Originally it was proposed that removing all @In annotations in the Session SFSB worked around the problem, however this does not appear to fix it in all cases (though this does appear to fix it in SOME cases).
--
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
18 years, 1 month