deploying to jboss in development

[tom.baeyens]

i have changed the deployment strategy a little bit. since multiple people are developing on different deployment artifacts, there is no single package that will get deployed by physical copy to the jboss deploy directory. instead all deployments are now done through JMX. this means that a file somewhere on your hard drive is deployed as if it were in the deploy directory. the advantage is that no jbpm deployments remain in the jboss deploy directory. so you can always start from a clean jboss by rebooting your jboss instance.

now, all the deploy targets, use jmx as a deployment mechanism. if you would like to add a target for deploying through physical file copy to the deploy directory, just add a new target called 'deploy.by.copy' or something like that.

does that make sense ?

does everyone agree that this is a good strategy ?

[tom.baeyens]

ah. i forgot to mention the target 'install.jboss.and.configure.jbpm' in the jboss/configuration/build.xml

that target will install the jboss in the local repository to the ${jboss.home} directory. then a jbpm server configuration is created as a copy of the default configuration. in the jbpm server configuration, the jbpm datasource and message queues, and logging configuration will be deployed.

so that target is the prerequisite for doing all other deployments as they might use one of these deployments.

[falazar]

How exactly does that work?
Can we get some stuff updated in the Wiki as well, or some good instructions.
I go the new CVS compiling but a little confused on what to deploy and how to deploy it.

James Ratcliff

[tom.baeyens]

look in jboss/configuration/build.xml for creating a jboss installation

you can shoot all other specific questions in this forum.

i know we should document this better, but that is a work in progress

[falazar]

One thing I was asked to post here is maybe not have the install and deploy remove the entire jboss/server directory, as we had another version in that directory running, and it removed all the setup for that version.

James Ratcliff

[tom.baeyens]

a simple unzip and overwrite of the jbpm deployment configuration is definitely a good idea.

the current targets need to remain, though. because for reproducing bugs, it is vital that we use the exact same set up. these targets are able to start from unzipping a jboss.zip file and then deploying jbpm from the sources in there.