jBPM-4.2 process archive deployment broken?
markroy Nov 24, 2009 2:50 PMjBPM 4.2
JDK 1.5
Windows XP SP2
JBoss 5.0.0GA
Oracle 10g
In jBPM 4.1, I was sucessfully able to deploy '.bar' process archives. In jBPM 4.2 this no longer seems to work. I understand there were some changes made in this area in 4.2. The Developer Guide now states that process archives should have the extension .jdpl and be dropped in $JBOSS_HOME/server//deploy.
I've tried this, but the archive does not seem to be deployed (nothing inserted into JBPM4_DEPLOYMENT). In the server.log, I see
2009-11-24 14:26:06,399 DEBUG [org.jboss.system.server.profileservice.repository.AbstractAttachmentStore] (HDScanner) No persisted attachment found for deployment AbstractVFSDeployment(esp.jpdl) with relative path: esp.jpdl-f0c23428c1aae5a7f2d4569a05803cf9\ 2009-11-24 14:26:06,479 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] (HDScanner) Add deployment: vfsfile:/C:/java/jbpm-4.2/jboss-5.0.0.GA/server/default/deploy/esp.jpdl 2009-11-24 14:26:06,479 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] (HDScanner) Scheduling deployment: vfsfile:/C:/java/jbpm-4.2/jboss-5.0.0.GA/server/default/deploy/esp.jpdl parent=null 2009-11-24 14:26:06,489 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] (HDScanner) Deploying vfsfile:/C:/java/jbpm-4.2/jboss-5.0.0.GA/server/default/deploy/esp.jpdl 2009-11-24 14:26:06,489 DEBUG [org.jboss.deployers.vfs.plugins.classloader.InMemoryClassesDeployer] (HDScanner) Dynamic class root for vfsfile:/C:/java/jbpm-4.2/jboss-5.0.0.GA/server/default/deploy/esp.jpdl is vfsmemory://5c4o4o5w-g1x6dk-g2f1h7r6-1-g2f24t5l-b6 2009-11-24 14:26:06,499 DEBUG [org.jboss.classloading.spi.dependency.Domain] (HDScanner) org.jboss.classloading.spi.dependency.Domain@185ad79{DefaultDomain} add module VFSDeploymentClassLoaderPolicyModule esp.jpdl:0.0.0 2009-11-24 14:26:06,499 DEBUG [org.jboss.classloader.spi.base.BaseClassLoader] (HDScanner) Created BaseClassLoader@9adbb8{vfsfile:/C:/java/jbpm-4.2/jboss-5.0.0.GA/server/default/deploy/esp.jpdl} with policy VFSClassLoaderPolicy@cf3d8e{name=vfsfile:/C:/java/jbpm-4.2/jboss-5.0.0.GA/server/default/deploy/esp.jpdl domain=null roots=[MemoryContextHandler@30554662[path= context=vfsmemory://5c4o4o5w-g1x6dk-g2f1h7r6-1-g2f24t5l-b6 real=vfsmemory://5c4o4o5w-g1x6dk-g2f1h7r6-1-g2f24t5l-b6]] delegates=null exported=[] <IMPORT-ALL>NON_EMPTY} 2009-11-24 14:26:06,499 DEBUG [org.jboss.classloader.spi.base.BaseClassLoaderDomain] (HDScanner) ClassLoaderDomain@1071521{DefaultDomain} registerClassLoader BaseClassLoader@9adbb8{vfsfile:/C:/java/jbpm-4.2/jboss-5.0.0.GA/server/default/deploy/esp.jpdl} 2009-11-24 14:26:06,499 DEBUG [org.jboss.aop.asintegration.jboss5.JBoss5ClassPoolFactory] (HDScanner) Created pool org.jboss.aop.asintegration.jboss5.JBoss5ClassPool@15189225 [class path: BaseClassLoader@9adbb8{vfsfile:/C:/java/jbpm-4.2/jboss-5.0.0.GA/server/default/deploy/esp.jpdl};] - dcl:BaseClassLoader@9adbb8{vfsfile:/C:/java/jbpm-4.2/jboss-5.0.0.GA/server/default/deploy/esp.jpdl} for loader BaseClassLoader@9adbb8{vfsfile:/C:/java/jbpm-4.2/jboss-5.0.0.GA/server/default/deploy/esp.jpdl} 2009-11-24 14:26:06,499 DEBUG [org.jboss.aop.asintegration.jboss5.AOPClassLoaderDeployer] (HDScanner) Adding AspectManager attachment org.jboss.aop.AspectManager@1e193f2 for AbstractVFSDeploymentContext@3188663{vfsfile:/C:/java/jbpm-4.2/jboss-5.0.0.GA/server/default/deploy/esp.jpdl} 2009-11-24 14:26:06,599 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] (HDScanner) Fully Deployed vfsfile:/C:/java/jbpm-4.2/jboss-5.0.0.GA/server/default/deploy/esp.jpdl
The Developer's Guide says I should see something like:
14:12:09,301 INFO [JBPMService] jBPM 4 - Integration JBoss 4 14:12:09,301 INFO [JBPMService] 4.0.0.Beta1 14:12:09,301 INFO [JBPMService] ProcessEngine bound to: java:/ProcessEngine
but instead I see:
2009-11-24 14:11:14,136 DEBUG [org.jbpm.jboss.internal.JbpmService] (main) JbpmService starting... 2009-11-24 14:11:17,881 DEBUG [org.jbpm.pvm.internal.cfg.ProcessEngineImpl] (main) jndi name java:/ProcessEngine is not bound 2009-11-24 14:11:17,881 DEBUG [org.jbpm.pvm.internal.wire.WireContext] (main) eagerly initializing org.jbpm.pvm.internal.id.DatabaseIdComposer 2009-11-24 14:11:17,932 DEBUG [org.jbpm.pvm.internal.wire.WireContext] (main) eagerly initializing org.jbpm.pvm.internal.jobexecutor.JobExecutor 2009-11-24 14:11:18,002 DEBUG [org.jbpm.pvm.internal.cfg.ProcessEngineImpl] (main) publishing jBPM ProcessEngine in jndi at java:/ProcessEngine
I'm using the default jbpm.cfg.xml and jbpm.hibernate.cfg.xml. I run the example JUnits sucessfully, so programmatic deployment appears to be working.
I'm guessing the jBPM Deployer is not getting invoked because it's not configured, but have no idea where to check.
Please help.