anonymous wrote : 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. anonymous wrote : 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. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3949686#3949686 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3949686 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
