1 Reply Latest reply on Jan 12, 2010 12:01 PM by kukeltje

[jBPM 4.2] does the "deploy by copy" really work ?

the_fredo Jan 11, 2010 10:21 AM

Hi,

In the dev guide , the following is mentioned :

"When jBPM is deployed on a JBoss instance, process deployments are treated like any other deployment artifact (i.e. *.war, *.ear) and processed by the JBPMDeployer. In order to deploy a process archive simply create a *.jpdl archive (zip file) that contains the process definition (*.jpdl.xml) and all required resources to execute the process (i.e. classes, property files):

      Bonanova:Desktop hbraun$ jar -tf OrderProcess.jpdl
      META-INF/MANIFEST.MF
      OrderProcess.jpdl.xml
      org/mycompany/order/*.class

But when I do that, nothing happens in my JbossAS 5.1.0 logs !

Any idea ? Did someone sucessfully deploy a process that way ?

Is .jpdl the correct extension ? are there some constraints on the archive ? (e.g. archive name must equal the .jpdl.xml file, or the *.jpdl.xml files must be at the root of the archive ? etc...)

my Jboss config should be ok since my appli.war deploys and runs correctly (I'm deploying the process sucessfully through the API

repositoryService.createDeployment() ...). The Jboss service is up and running (but produces only that piece of log :

2010-01-11 15:12:25,763 INFO [org.jbpm.jboss.internal.JbpmService] (main) JbpmService started )

thanks !

Fred

1. Re: [jBPM 4.2] does the "deploy by copy" really work ?

kukeltje Jan 12, 2010 12:01 PM (in response to the_fredo)

No, see jira
Actions