I was just looking at that as well. It seems to me that the approach is broken (redundant).
As far as i can read the current code, the JbpmConfiguration that is put in JNDI is never used. When the JbpmConfiguration.getInstance() method it used, it lazy initializes a JbpmConfiguration based on the resource 'jbpm.cfg.xml'. This configuration is cached in a static variable in JbpmConfiguration. So the jBPM configuration used is the one that is cached in the JbpmConfiguration static member rather then the JNDI one. This lead to the following basic question: "what is the benefit of putting something in JNDI ?" http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3942144#3942144 That thread also discusses something relevant. Namely: "should we create a JCA .rar that publishes JbpmConfiguration into JNDI" so that we have a portable way of deploying jBPM on an app server. So for now, I don't see a problem with the current approach. (except for the redundency that the JbpmConfiguration that is published in JNDI is never used) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3942442#3942442 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3942442 ------------------------------------------------------- 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
