jaikiran pai [http://community.jboss.org/people/jaikiran] created the discussion "Re: How to use external jars not contained in JBoss" To view the discussion, visit: http://community.jboss.org/message/563780#563780 -------------------------------------------------------------- -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/563780#563780] Start a new discussion in JBoss Microcontainer at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Ales Justin [http://community.jboss.org/people/alesj] created the discussion "Re: How to use external jars not contained in JBoss" To view the discussion, visit: http://community.jboss.org/message/564124#564124 -------------------------------------------------------------- Unfortunately the community docs are poor wrt this issue, but support ... ;-) But let's try to make this work anyway. Yeah, or any UrlIntegrationDeployer (including it) would do -- depends on what you need. I suggest you first read this article about VDF:** http://java.dzone.com/articles/jboss-microcontainer-virtual-deployment-fr... http://java.dzone.com/articles/jboss-microcontainer-virtual-deployment-fr... to get a better feel for how deployers actually work -- if you haven't already. Each deployer checks every deployment, sub-deployment, sub-sub-deployment, .. So, when you write your own "integration" deployer, make sure you short circuit asap, only applying integration logic to (sub*)deployments that really need it. The logic of adding external lib is already written in the UrlIntDeployer, you just need to fill in the blanks. Then simply deploy this new deployer in deployers/ dir as we do for some our JBoss deployers -- see *-jboss-beans.xml files. Deployer is nothing than a MC bean, and the MC kernel will pick it up automagically. ;-) What this UrlIntDeployer does it simply alters spec defined classpath with additional resources; e.g. your ext lib. So, when constructing deployment's classloader we use this classpath, not really bothering where the resources come from. If the resources are already shared by some parent classloader or common classloading domain, and your classloader's lookup first delegates to them (e.g. plain cl behavior or non-web behavior), you should also be fine with no dup classes loaded aka can easily be shared. HTH? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/564124#564124] Start a new discussion in JBoss Microcontainer at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]