06-06-2010 03:49 PM
06-07-2010 01:47 AM
06-07-2010 09:18 AM
Activiti's API looks very similar to jBPM4's API but since Activiti is a BPMN-2.0-engine the file format of the XML format is BPMN-2.0-XML and thus is completely different from jBPM which uses its own process definition language (jPDL).Oh I see, the Java code (API) is similar, is nice to know that now, about XML I understood, but I think that should be easy to understand quickly its syntax, right?
Please re-phrase the second part of your post since I have troubles understanding what you want to know.OK, sorry for my English, I mean about this
And since Spring thinks work closely together with Activiti I want to know if critical changes about migration about knowledge and code would existsIf I already have a simple BPM/jPDL process with jBPM and Spring, it would be very hard or painful migrate to Activiti with Spring?
06-09-2010 03:54 AM
06-09-2010 08:27 AM
migrating the process xml files (even manually) is not that hard.
but the hard part will be to migrate the runtime data.
06-14-2010 05:08 AM
06-15-2010 03:07 PM
Manuel, Tom means the data in your jBPM database: the running process instances, tasks, etc. That's the hard part to migrate.Hello Joram
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.