There is no xml based export/import available, nor is it on the todo list. I do not know of people having any experience at all with migrating instances from one db to another even with a dump...
If it is important (the xml based solution), please file a jira issue for it.
I know in 3.1.1 there was the JpdlXmlWriter class, though it is deprecated, and says "xml generation was never finished and will be removed in the future."
If your process is simple it might work.
That was for the processDefinition, not a processInstance with all its log information etc...
This JpdlXmlWriter was made obsolete because the process was stored in the db as full text. So you can retrieve it like the processImage or so.
The advantage of this is that you can turn off validation of the process in the server and add custom info to the process!!!
This should (imo) be solved in a better way in the future but it can be handy as it is is now.
Oops, sorry, I didn't read instance, i just saw process and my mind took control there :)
Yeah, we wish the JpdlXmlWriter (or something similar) was implemented, because we are programmatically modifying our process definitions before we deploy it. It'd be nice to get a new xml back which reflects all our changes :)
Why not simple create an xmlbeans representation of the xsd and use that before deploying. Then you have the option to get string xml back.
i'm having a problem with the generated code through XML Beans (xmlbeans.apache.org).
The problem begin when i want to add a variable to a controller defined into a task node.
well, i say: "xmlbeans isn't working fine", but...Surprise!!!! the element isn't added in the element from which depends into the xsd definition file.
of course that this is not a bug of jbpm, because ,by example, jbpmServer would not working.
i read the previous post that recommend the use of xmlbeans.
could you please tell me how to resolve this problem???
thank you from Argentina