There is some little documents within "doc" folder of the download jBPM BPEL. The document are actual step by step using ANT.
Wish helpful to you.
Thanks for your reply !
I tried the Hello example but I can't go through the whole process : I've got a JpdlException thrown about a file called processdefinition.xml when I execute
$> ant generate-service
... [no processdefinition.xml inside process archive]
I don't know why and, in fact, as the whole example is automated with Ant, it is not what I really look for ; but, nevermind, I will try to understand how to perform by hand Ant tasks.
I've got a JpdlException thrown about a file called processdefinition.xml when I execute
$> ant generate-service
I don't know why
I think you did not quite follow the instructions in the user guide :-) Section 2.4 guides you through packaging and deploying the jBPM BPEL service. Section 3.1.2 of the user guide tells you about some values you need to change in build.properties to make the Ant scripts aware of your installation directories.
You see that exception because the core jBPM library does not know about BPEL documents. By default, it looks for a jPDL document named processdefinition.xml in the process archive. The BPEL module configures jBPM to read BPEL documents instead, but jbpm-bpel-x.jar must be in your classpath for the new behavior to take effect.
as the whole example is automated with Ant, it is not what I really look for
Some remarks about this:
Most targets just copy files and package them in the format described in the documentation.
Target wscompile wraps famous tool from the Web Services Dev Pack. You might as well execute it directly with the arguments that appear with the Ant script.
We defined three custom tasks. Two of them contact the servlets described in jbpm-bpel.war. This web application is a nested deployment of the jBPM BPEL service.
webdbschema contacts the servlet mapped to /dbschema. It creates/drops the database schema using the hibernate configuration files included in the service.
webdeploy contacts the servlet mapped to /deploy. It reads a process definition from an archive and saves it in the database.
Finally, servicegen is a wrapper for our service WSDL document generation tool.
you did not quite follow the instructions in the user guide :-) ... jbpm-bpel-x.jar must be in your classpath
Oh... What for a stupid mistake ! I think I should avoid any alcoholic drink !
Everything allright now, works well.
Thanks for these explanations about Ant tasks (really useful to understand the whole process).
There is no need to avoid alcaholic drinks, just do not work, drive, have sex at the same time
Can I use JBPM-BPEL Alpha4 as product level or it just a experimental edition.
Since if we go for ActiveBPEL, it requires JBOSS4.0.3SP2 which use Axis, but unfortunately we just upgrade to 4.0.4 GA. We currenlt use JBOSS WS not AXIS.
We have some customers that use it as product level. We are not feature complete yet but what is already there is rock solid.
jBPM BPEL builds on top of the SAAJ, JAX-RPC and WSEE APIs, all part of J2EE 1.4. We are not tied to any particular web services stack.
That said, the primary testing target for Alpha 4 was JBoss 4.0.3 SP1. For Beta 1, we are focusing on JBoss 4.0.4. While smooth, the transition was not transparent due to some idiosyncrasies of the old Axis-based stack.
The JBossWS team tells me the new stack behaves just like the RI, so hopefully Beta 1 is more portable to app servers from other providers.