[jboss-dev-forums] [Design of JBoss jBPM] - Re: Undeployment in JBosss Deployer

[heiko.braun@jboss.com]

I 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. Hence it can be deleted right away, IMO. 

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. 

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238744#4238744

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238744