Seems there is no way to do that.
I suggest you to use a in-memory database, e.g. HSQLDB. to test process in memory.
Okay. Does the HSQLDB act only as an in-memory database, or does it depend on how you configure it?
Please refer the default configuration in jbpm.hibernate.cfg.xml. In default, jbpm4 are using in-memory mode to do all of test on HSQLDB.
Actually there are three running modes on hsqldb. In-Memory, File-based and server-client. You could get more information on hsqldb official website.
Hi, I'm evaluating jBPM for use in controlling the processing of a single HTTP request to a web application (we want to have configurable bucket testing of different request-processing flows), so I'm also interested in how to disable persistence. It seems that even persisting to an in-memory database would involve a fair bit of needless (in my case) overhead to read/write execution state through layers of jbpm, jdbc, and hsqldb on every transition in the workflow.
Is it definitely not possible to disable this altogether, even when using the low-level client API? If it can be disabled, where specifically in jbpm.default.cfg.xml or included files is this done?
Also, if it's not possible to disable DB persistence in jbpm4, is it in jbpm3? How / where in the config. file?
Since I hadn't done like that before. I don't know what will happened if we disable the DbSession.
If you want some documentation about have to create a process defintion programmaticly, I find some snippet from developer guide, I think it may be some help.
If you got some result, could you send some reply here? Thank you very much.
Thanks HuiSheng. I'm about to go on vacation and am not sure when I'll get back to this, but will update this board with any results when I get them.