The approach that I currently take is to just include the jars in my ear, for each component that then requires access to the jar I add a Class-Path entry listing the jars used.
I haven't tried putting the jars in a different folder within the ear and referencing the folder/jar in the manifest, if that worked you may get away with just changing the manifest files to refer to the jars in the structure you use for weblogic. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3847638#3847638 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3847638 ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
