PDA

View Full Version : JBoss 4.0.2 : problem '${flowExecutionId}' birthdate sample



Jokum
Jul 28th, 2005, 04:03 AM
When using the Web Flow birthdate sample on JBoss 4.0.2 I keep getting this exception :


11:01:02,531 WARN [RequestProcessor] Unhandled Exception thrown: class org.springframework.webflow.execution.NoSuchFlow
ExecutionException
11:01:02,531 ERROR [[action]] Servlet.service() for servlet action threw exception
org.springframework.webflow.execution.NoSuchFlowEx ecutionException: No executing flow could be found with id '${flowExec
utionId}' -- perhaps the flow has ended or expired? This could happen if your users are relying on browser history (typi
cally via the back button) that reference ended flows.; nested exception is java.lang.IllegalStateException: No session
attribute 'org.springframework.webflow.execution.FlowExecuti on.${flowExecutionId}' found
java.lang.IllegalStateException: No session attribute 'org.springframework.webflow.execution.FlowExecuti on.${flowExecuti
onId}' found
at org.springframework.web.util.WebUtils.getRequiredS essionAttribute(WebUtils.java:204)
at org.springframework.webflow.execution.servlet.Http SessionFlowExecutionStorage.load(HttpSessionFlowEx ecutionSt
orage.java:67)
at org.springframework.webflow.execution.FlowExecutio nManager.onEvent(FlowExecutionManager.java:424)
at org.springframework.webflow.struts.FlowAction.exec ute(FlowAction.java:176)
at org.apache.struts.action.RequestProcessor.processA ctionPerform(RequestProcessor.java:419)
at org.apache.struts.action.RequestProcessor.process( RequestProcessor.java:224)
at org.apache.struts.action.ActionServlet.process(Act ionServlet.java:1194)
at org.apache.struts.action.ActionServlet.doPost(Acti onServlet.java:432)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:717)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:810)
at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doF ilter(ReplyHeaderFilter.java:81)
at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.CustomPrincipalValve .invoke(CustomPrincipalValve.java:39)
at org.jboss.web.tomcat.security.SecurityAssociationV alve.invoke(SecurityAssociationValve.java:153)
at org.jboss.web.tomcat.security.JaccContextValve.inv oke(JaccContextValve.java:59)
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.invok e(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(H ttp11Processor.java:856)
at org.apache.coyote.http11.Http11Protocol$Http11Conn ectionHandler.processConnection(Http11Protocol.jav a:744)
at org.apache.tomcat.util.net.PoolTcpEndpoint.process Socket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread .run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:534)


When using the same war on Caucho Resin all is working just fine.

Can anybody please help me with this?

Kind regards,

klr8
Jul 28th, 2005, 10:43 AM
Is JBoss 4.0.2 a Servlet 2.4/JSP 2.0 compliant container? Seems like it is not evaluating the "${flowExecutionId}" in the JSP and passing it as-is back to the server. The samples use JSP 2.0 for elagance and clarity, so you'll need a JSP 2.0 capable container to run them.

Erwin

gmatthews
Jul 28th, 2005, 06:02 PM
Is JBoss 4.0.2 a Servlet 2.4/JSP 2.0 compliant container?

Yes, as long as you've got web.xml correctly configured, and are using the correct JSTL Standard 1.1 jar.