Class loaders are nested to provide isolation. WARs use war-local resources, EARs use ear-local, ditto for SARs and so on. The configuration is next followed by jars or classes in the server.
WAR files have the added requirement of an option that stipulates that no classes outside of system classes will be used. It's a security thing. The best solution is to use EARs to aggregate EJBs and WEB resources. You can also get away with a "java" modules in JBoss for loose jars specified in your application.xml, however, you should use your MANIFEST.MF to specify the dependencies between loose jars and your EARs 'n WARs. I create one manifiest for every jar and specify the dependencies (one level deep) in each. This eliminates duplicate jars and classes entirely, much cleaner. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873064#3873064 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873064 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
