yes. that all makees sense.
let's start with trying to get as much as possible of jbpm to run in memory mode through the normal service based api.
still remains to be seen how well the current implementation already supports this strategy.
if all we need is some memory implementations of the some sessions and small patches here and there to head to make this work then i want to include those patches very much. theoretically the design should support it...
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242462#4242462
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242462
What I'm thinking of is, to build my own custom ProcessRepository. This process repository would be held in memory, as I only want latest process definitions to be used. Then I would like to instantiate different ExecutionServices, with different persistent strategies for executions and history (memory, db) to enable asynchronous process executions (persistent mode) and synchronous process execution. (memory execution, and persistent or without history).
I'll try to start with the on memory process repository, trying to hold ProcessDefinitions in Memory. And then, I think Iĺl try to configure an ExecutionService, without history.
Any thoughts?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242386#4242386
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242386
with the jbpm core, it should be possible to build out all execution modes as described in http://www.jboss.org/community/wiki/jBPM4ExecutionModes
i believe that you are referring to the 'Memory' execution mode, right ?
the direction we're thinking in for that use case is to use the ProcessBuilder to create process definitions. Probably we can leverage the JpdlParser for that as wel. That will immediately give most of jPDL features instead of having to start from an empty PVM. Maybe some dependencies on the environment configuration sneeked in here or there.
Our current idea is to use methods on the objects themselves for the memory execution mode, and skip the services api's
It would be great if you could try that direction and see where you run into problems.
Keep us posted
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242385#4242385
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242385