Now we are. I see no other way but for you to use that version number. You can
set it in code when you load the process definition.
...
JbpmSession jbpmSession = jbpmSessionFactory.openJbpmSession(conn);
try {
// ... and begin a transaction on the persistence session
jbpmSession.beginTransaction();
ProcessDefinition definition =
ProcessDefinition.parseXmlResource(processName+".par/processdefinition.xml");
definition.setVersion(version);
// Save the process definition in the database
jbpmSession.getGraphSession().saveProcessDefinition(definition);
// Commit the transaction
jbpmSession.commitTransaction();
}
finally {
// And close the jbpmSession.
jbpmSession.close();
}
...
I believe the version number remains undefined unless you set it - except when
you use a par file. So, yes, you need to keep track of the version numbers in
production. Hey, its never easy.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3916876#3916876
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3916876
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
