I've been thinking about this a bit the last day. Here's the advantages, IMO, of the new deployer I'm proposing: * Easier for newbie to get start. One last thing they have to worry about. * Easier for development * Less configuration * Doesn't impair other jBPM deployment options * gets in line with how other JEMS projects deploy into JBsos Disadvantages: * Not portable to other application servers. (Until we get JBoss Embedded going). * I don't think this will work well with class versioning unless we add metadata to the .par (like a version number) My questsions are: * How often is versioning used? * How many versions are live at one time? How many versions do applications usually have in play? One last thing: * Maybe with this new deployer, versioning should be turned off by default? * Should a piece of metadata be added to the deployment to say whether or not it should be versioned or just overwrite the old deployment? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052653#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...