What problems did you encounter?
I have installed jBPM first time without any issues.
The jBPM install does not work with JBoss 3.2.6 or 4.0. It works fine on 3.2.5, though. I'm not sure what changed in 3.2.6 to cause this error.
This is probably a lib conflict. We will be resolving this shortly.
If you can't wait, you can try to take the hibernate and commons libs from the jboss 3.2.6 (or higher) and overwrite the corresponding libs in the jbpm distribution. then perform a clean build.
these issues with the ejb-wrapper should not be linked to the overall engine stability. focus has been on the core engine. the ejb wrappers were only included to show that jbpm was deployable on a clustered jboss. in the future, jbpm will remain deployable outside of jboss, but of course, we will work hard on smooth integration in the coming months.
Thanks for the replies. However, I'm still not clear what is the recommended path forward with workflow solutions and JBoss.
I've seen JBoss make announcements like this with other products, but they don't go very far.
Is jBPM going to be the recommended way forward with workflow on JBoss? Or, is Oak Grove's Reactor the recommended way forward? Or, something else?
Having worked with Weblogic Integration, Staffware, and webMethods, I can say that the open source solutions are orders of magnitude behind the commercial offerings. However, when you are on a low-budget program, you may not be able to choose a commercial offering (or at least not an expensive one).
JBoss jBPM is the future direction.
JBoss jBPM is the only workflow engine part of the open source set of federated projects under the JBoss umbrella.
The other workflow engines are partner agreements.
"Is jBPM going to be the recommended way forward with workflow on JBoss?"
behind? yes and no : JBoss jBPM is innovative ahead of the other products you mention. JBoss jBPM is behind commercial implementation when it comes to completeness.