1 of 1 people found this helpful
I assume that what you are describing is problem with process deployment not the jbpm itself, correct?
As far as I know there is no jboss integration with 4.4 release. So probably that causes JBoss to complain since it can't find proper deployer for jpdl.
Either deploy process manually or try to get jboss integration packages from previous releases (4.0 or 4.1).
Thanks, Maciek. I don't have much free time to test it thoroughly at the moment, but a quick test resulted in a class not found exception (org/jbpm/integration/spi/DeploymentAdaptor). I have placed jbpm-jboss4.jar into the server lib folder and added JBPMDeployer into jboss-service.xml (in deploy/jbpm/jbpm-service.sar/META-INF):
<mbean code="org.jbpm.integration.jboss4.JBPMDeployer" name="org.jbpm:service=JBPMDeployer"> </mbean>
I'm not sure if exception is related as there is a strong possibility I may have accidentally broken my setup.
I'll get back to you as soon as I'll get some time to play with jbpm.