Heiko. anonymous wrote : | would expect a process deployment artifact to contain all the classes and resources a process requires for execution. So, if you rely on the classloader you receive from the AS deployer framework and the the deployment artifact get's removed, then you basically leave the process in an unusable state. | Right, this is why it is suspended. So it cannot be signaled any more. anonymous wrote : | Hence it can be deleted right away, IMO. | Not right, because we just don't want to delete the unfinished process instances. anonymous wrote : | But of course, if you keep writing class information to the database and deal with classloading and scoping on your own then you don't have this problem in the beginning. But I don't believe you easily leverage advanced AS features if you keep providing custom solutions for things that the AS already provides. | This has nothing todo with it. I agree, classes should go in the ear or whatever. See answer above. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238756#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...