"koen.aers(a)jboss.com" wrote : Hm, does this not imply that you are forced to use Java EE? I think that much of the elegance of the current system comes from its lightweightness and its ability to embed itself in whatever system. It would be a pity to lose that IMO. Well, storing the archive data inside the database isn't exactly lightweight. :-) I don't think you'd have to use java ee deployers if you didn't want to, I'm just using that as an example. As long as the engine knows where to pick up process definitions it should work. This is (I think) actually a simpler use-case of javaee deployers, since there's no special startup or shutdown action to be taken; it just has to store the process information in a Map. Likewise the standalone version can just read the process definitions from the filesystem; it already has the plumbing to do this today as far as I can see. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999173#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...