mroony: if the ears are completely independent "units" (ie, they don't rely upon any functionality the other provides), then you can scope them so you can deploy different versions of your util.jar.
chap 2 of the jboss admin book talks about this and how the class loader works in general. mathias: yes and no.... you can deploy the jar into the deploy directory, and then if you need to add a new method, you are free to do so. since you will have to redeploy the ear w/ the jar (containing the interfaces) anyway, you'll have no issues. where it can get more complicated is if you have another ear (B.ear) deployed that may rely upon functionality of the newly updated ear (A.ear see above). if you added new methods, once you redeployed A.jar and A.ear, you would also have to "touch" B.ear to cause the classloader to cycle so it doesn't have any stale references to A.jar. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3834278#3834278 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3834278 ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
