Announcement Announcement Module
Collapse
No announcement yet.
JBoss 4.0.2 : problem '${flowExecutionId}' birthdate sample Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • JBoss 4.0.2 : problem '${flowExecutionId}' birthdate sample

    When using the Web Flow birthdate sample on JBoss 4.0.2 I keep getting this exception :

    Code:
    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.NoSuchFlowExecutionException: 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.FlowExecution.${flowExecutionId}' found
    java.lang.IllegalStateException: No session attribute 'org.springframework.webflow.execution.FlowExecution.${flowExecuti
    onId}' found
            at org.springframework.web.util.WebUtils.getRequiredSessionAttribute(WebUtils.java:204)
            at org.springframework.webflow.execution.servlet.HttpSessionFlowExecutionStorage.load(HttpSessionFlowExecutionSt
    orage.java:67)
            at org.springframework.webflow.execution.FlowExecutionManager.onEvent(FlowExecutionManager.java:424)
            at org.springframework.webflow.struts.FlowAction.execute(FlowAction.java:176)
            at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419)
            at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224)
            at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1194)
            at org.apache.struts.action.ActionServlet.doPost(ActionServlet.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.internalDoFilter(ApplicationFilterChain.java:252)
            at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
            at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
            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.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
            at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:153)
            at org.jboss.web.tomcat.security.JaccContextValve.invoke(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.invoke(StandardEngineValve.java:107)
            at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
            at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
            at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
            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:534)
    When using the same war on Caucho Resin all is working just fine.

    Can anybody please help me with this?

    Kind regards,

  • #2
    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

    Comment


    • #3
      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.

      Comment

      Working...
      X