Hi, This is a variation on the question of deploying the same app twice. Can I tell a war to a use classloader/loader repository defined in a seperately deployed ear?
I have a jar that both an ear and war need to share. The twist is that the war is not in the ear, it is deployed seperately. If everything was packaged together, I can define my loader repository and deploy the app again with another loader-repository (and jndi bindings), everything works great. If I don't deploy the second app, I can move the jar directly into the deploy directory and the war and ear share it, no problem. I can't figure the correct recipe for deploying the war and the ear seperately, twice, with different loader repositories.... So what I would like hibernate.ear hibernate.sar pojos.jar app.war (that knows to use hibernate.ear loader-repository) hibernate-test.ear hibernate.sar pojos.jar app-test.war (that knows to use hibernate-test.ear loader repository) Alex <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3824255#3824255";>View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3824255>Reply to the post</a> ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
