"Assenza, Chris" <[EMAIL PROTECTED]> writes:
> Okay...I'll rephrase that last one I sent. :) You won't be able to deploy
> the EAR the way you want without properly using the Application Deployment
> Descriptor (application.xml). Have you tried doing this?
>
> Here's a sample one I use for JBoss 2.0 w/ Tomcat 3.2b7, goes in META-INF of
> the EAR's contents.
>
> <?xml version="1.0"?>
> <!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE
> Application 1.2//EN" "http://java.sun.com/j2ee/dtds/application_1_2.dtd";>
>
> <application>
> <display-name>App Name</display-name>
> <module>
> <web>
> <web-uri>Warfile.war</web-uri>
> <context-root>/usermanager</context-root>
> </web>
> </module>
>
> <module>
> <ejb>EJBJar.jar</ejb> <!-- Could be multiple -->
> </module>
> </application>
Yes, my application.xml should be ok. It looks like this:
<?xml version="1.0" encoding="ISO-8859-1"?>
<application>
<display-name>usermanager</display-name>
<module>
<web>
<web-uri>usermanager.war</web-uri>
<context-root>/usermanager</context-root>
</web>
</module>
<module>
<ejb>usermanager.jar</ejb>
</module>
</application>
And with the duplicated jars (usermanager-client.jar - interfaces)
and (struts.jar) (in ear's root and war/WEB-INF/lib) it works.
But I don't like duplicating those jars, only to support jasper's
jsp compiling. (I will haev to look for jasper's docu, perhaps
I can write the ant task)
--
gR
