Hi Kris,

our company has been using jBPM3.x for a while. Some months ago i have been evaluating jBPM 4.x and drools flow to choose a framework for our new application. while i liked a lot of features in drools flow, i have some concerns regarding the persistence solution (process is in a stateful knowledge session and serialized in a single blob field in the database). here are some comments to the proposed jBPM5 architecture:

- support of BPMN2.0 integration is highly appreciated
- integration of an ioc container would be nice (e. g. spring ioc)
- osgi support
- possibility to run a process without drools, persistence should not depend on persisting a stateful knowledge session
- possibility to use transient data in a process, data that is not automatically persisted (we have long running processes, where data is also changed outside of the process scope - we have to insert some facts into the session per request)
- possibility to change the definition of a running process instance (changes on the fly when you are executing a process, persisting such a "dynamic" process would mean, to also persist the process definition for each instance. we could define a "standard" workflow, with the possibility to allow the user/application to add some steps to the running process)

kind regards,
Walter