not persisting instances

[tbee]

In the documentation it says that persistence is optional. Now, I have some workflows I would like to persist and some I do not, within the same enviroment. I though that

lJbpmContext.save(lProcessInstance);

Would trigger the storage, but appearantly that is not needed and any workflow is persisted when created (if hibernate is configured). Is that correct? Or is it possible to keep a workflow instance in memory only?

[kukeltje]

you have just one of the options with one instance of the engine.... one instance of the engine is one configuration. So creating a context with a different configuration gives you what you want.

[tbee]

"kukeltje" wrote:
you have just one of the options with one instance of the engine.... one instance of the engine is one configuration. So creating a context with a different configuration gives you what you want.

Would you mind being just a tad more verbose for the new and uninitiated?

Should I make two configuration files and use a name in the getInstance with a filename? Or am I supposed to integratie two configuration in one and use the createcontext with an identifier. Both seems to do something in that direction.

[kukeltje]

Correct, both options would work. Although for the latter it could be that some configuration items are global and not within a context...

[kukeltje]

Correct, both options would work. Although for the latter it could be that some configuration items are global and not within a context...