For my Tapestry / jBPM integration project, I stumble onto this problem: JbpmContext contextA = JbpmConfiguration.getContext(); | JbpmContext contextB = JbpmConfiguration.getContext(); | | ProcessInstance instance = contextA.createNewProcess(name);
------------> bluhhh... This happens because I would like to have a context available during all the steps of the render of each page. When I transfers from page A to page B, page B is created and startes the rendering process (i.e. contextB is created) before I have created the new ProcessInstance. But creating a second context makes the first one behave "funny" and fail the creation (return id=0). Should I have shorter spanned contexts: one for every component I need to render? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3940402#3940402 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3940402 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
