"bill.burke(a)jboss.com" wrote : I'm reworking the JBoss+jBPM configuration and deployment structure: | (...) | 2. Getting up and started with jBPM is painful in a JBoss environment. | (...) | b) You need to modify your ant build to save your .jpdl into the database so that the jBPM server can pick things up. OR you do some other manual or programmatic process to get your process definitions in the database. | You can deploy process definitions using the web console or graphical process designer as well, but yeah... "bill.burke(a)jboss.com" wrote : I want to create a ProcessDefinitionDeployer for jboss. This will work like the SAR, EJB, EAR, etc... deployers. Users would be able to deploy a .jar file named "xxx.bpm" or a foo.jpdl.xml file. The jar file would contain a "META-INF/jbpm.jpdl.xml" file within it and any classes that could possibily be used by the process definition. At deployment time, the JBPM deployer would calculate a hash for hte .xml file. If this hash matches a previously deployed .xml file nothing is done. If it is a new hash, a new version of the process definition is saved to the database. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051933#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...