On 6/15/06, Mario Rübsam <[EMAIL PROTECTED]> wrote:
Is the classloading behaviour without adding the Classpath in MANIFEST.MF a bug in 1.1rc1 ? Should I file a Jira?
Please do. Thanks, Aaron
Mario Rübsam wrote: > I had a working EAR for 1.0 with this structure > > app.ear/ > app.jar > cpa.jar > found.jar > webclient.war > > I referenced the jars from the webclient.war/META-INF/MANIFEST.MF > Classpath: app.jar cpa.jar found.jar > > When I deploy this EAR in G 1.1-rc1 I get ClassNotFoundExceptions. > > When I put the JARs into the webclient.war/WEB-INF/lib everything > work fine. But this is not an option because I have some other > WARs to deploy in that EAR. > > A general class loading and dependency resolution description for > EARs would be very helpful. > > The next thing I found out is that the DB connector dependency > must be placed into the geronimo-application.xml when deploying > as an EAR. When deploying as an WAR the dependency is good in > geronimo-web.xml as stated in the docs or the console example. > > Thanks, > Mario > > > [EMAIL PROTECTED] wrote: >> >> >> >Which G version are you running because in 1.1-rc1 adding the jars to >> >the war MANIFEST classpath stopped working for me? >> >> 1 not 1.1 >> >> I can't get my app to deploy in 1.1 for other reasons but if adding >> jars to the mainfest classpath is broken in 1.1 this is a fairly >> serious bug. >> >> Target >> >> www.targetgroup.net >> >> ********************************************************************** >> >> DISCLAIMER. >> >> This message is intended only for the use of the Addressee and may >> >> contain information that is PRIVILEGED and CONFIDENTIAL. >> >> If you are not the intended recipient you must not copy, >> >> distribute or take any action or reliance upon it. >> >> The content of this message may also contain personal >> >> views of an employee of this company and does >> >> not necessarily represent the view of the company. >> >> ********************************************************************** >> >> This message has been scanned by Norton Anti-Virus. >> >> It has also been scanned by MAILsweeper to enforce our e-mail >> >> policy. If you have any concerns or comments about the content >> >> of this message, please e-mail [EMAIL PROTECTED] >> >> ********************************************************************** >> >> >> _____________________________________________________________________ >> This email has been scanned for all viruses by the MessageLabs Email >> Security System. For more information on a proactive email security >> service working around the clock, around the globe, visit >> http://www.messagelabs.com >
