No this possibility was available in earlier versions of jBPM but has been removed. Why exactly would you want to do this?
Here is I scenario where I want all the process definitions in XML : I want to provide a feature to export the latest definitions for all the currently deployed process definitions.
Could you tell us how to load the Process Definitions from the DB and then convert them back to XML form so that one can view them offline too in the Process Designer ?
We have an Admin-Interface in our Application, where we want to provide an overview of all deployed ProcessDefinitions and versions of ProcessDefinitions.
One part of this feature should be the ability to look up the XML-Source of these Definitions.
It wouldn't be a problem, if there only were one version of each ProcessDefinition but as there could be more than one version of a ProcessDefinition in the database we need the functionality described in my first thread.
If this feature is not present -- could someone provide a list of all tables in the database that contain definitions, so that we can back up these tables to cover for an eventuality where the database gets corrupted and the process definition files are not upto-date, etc.
Why do you want to just backup the definitions? Why not the whole database?
Besides that, if your process definiions are not up to date, it's difficult to change them since you do not know your startingpoint
Currently there is no way to generate the processdefinition back from the database (you should use cvs to keep the latest versions!) Another option is to write your own deployer and keep the .par files there. These contain the processdefinition in xml format.
Thanks for the responses. I agree with you that and be assured that we are using CVS to store all process artifacts.
I was only looking out for a quick way to replicate the setup on another machine. Yes, I can dump the whole database and get going. But I dont want the instance data.
That is the reason, I was trying to understand the list of tables that contain definition data v/s instance data. Its only for my understanding.