You've mostly got it right. jars that you want to be seen globally by all deployments go in server//lib, Where is usually "default", "all", or "minimal".
You should not put jar files in jboss-4.0.1/lib. I suspect that the reason you don't see the dot.com:loader=jpi-jboss-iv-ejbs.ear repository in the JMX console is that the XML for your jboss-service.xml looks backwards. According to the DTD, loader-repository goes before classpath. Try adding this to jboss-service.xml so the xml will be validated: <!DOCTYPE server | PUBLIC "-//JBoss//DTD MBean Service 4.0//EN" | "http://www.jboss.org/j2ee/dtd/jboss-service_4_0.dtd"> | For what you want to do with the WAR files, you need to have useJBossWebLoader=false. This will make your web apps use the Tomcat class loader which doesn't know anything about loader repositories. It will look at the web app first and then ask its parent to load the class if it is not inside the WAR. Loader repository settings only take effect on the root context class loader. That means that if you have an ear inside a sar then only the class loader repository settings for the sar have any effect. The same is true for a war or ejb.jar inside an ear. useJBossWebLoader=false, however, does have an effect because it is outside the realm of loader repositories. When you put a loader-repository setting in a non-root deployment, you will get a warning message in the server.log. Stan Silvert JBoss, Inc. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862620#3862620 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862620 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
