Ok figured out how this is done in JBoss and implemented the same strategy in
WLS and it appears to work. In the meantime saw some nice bugs in JBPMService
class not closing initial context and ignoring supplied jndi name..
View the original post :
OK seems to be added between 4.1 and 4.2 so upgrading to 4.2 should hopefully
solve our issues with undeployment.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4269827#4269827
Reply to the post :
Hi,
I am attempting to deploy a JBPM Application on Weblogic 10.3. Thus far this is
working however we have a requirement to use MDB to interact with JBPM.
Obviously we need the JBPM initialized from the web application and this is
working. However after reading the JBPM docs we decided to
Hi,
We are seeing issues when redpeloying our jbpm EAR into weblogic with recursive
JTA exceptions. This is no doubt due to the fact there seems to be no hooks to
gracefully close the jbpm Engine down with we undeply the EAR.
The javadocs for jBPM 4 (we are using jbPM 4.1 due to subflow
