This content has been marked as final.
Show 2 replies
-
1. Re: Classloader issues: Need to share libraries across web a
jaikiran Jul 18, 2007 3:32 PM (in response to kpalania)So, I need to move these to the EAR level (WAR and SAR applications are deployed as part of this EAR). How can I do that and what are the steps involved?
You will have to create an ear file containing the war file and the sar file. Additionally, you will require a application.xml file and a jboss-app.xml file (both in the META-INF folder of the ear). The application.xml will contain something like:<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN" "http://java.sun.com/dtd/application_1_3.dtd"> <application> <display-name>My Application</display-name> <module> <web> <web-uri>myApp.war</web-uri> <context-root>/myApp</context-root> </web> </module> </application>
Then the jboss-app.xml will contain:<jboss-app> <loader-repository> tap:loader=myApp.ear <loader-repository-config> java2ParentDelegation=false </loader-repository-config> </loader-repository> <module> <service>myAppSar.sar</service> </module> </jboss-app>
Replace myApp.war, myApp.ear and myAppSar.sar without appropriate names of your archives.
The loader-repository in jboss-app.xml is optional in the jboss-app.xml, retain it if you want classloader isolation for the ear file. -
2. Re: Classloader issues: Need to share libraries across web a
kpalania Jul 18, 2007 8:14 PM (in response to kpalania)thanks very much jaikiran! i'll give this a shot and see how it goes. will respond with questions if there are some issues. thanks again!