Well, the most I can tell you about it is that check the following issues:
1) the import statement (import xxx.yyy.className) 2) check the rigth path inside the jar file. 3) check that /lib if you are using unix-based system is in lowercase and /WEB-INF in uppercase. 4) if you are using that class inside a jspBean tag remember to specify the class That's all I can tell about, try it and good luck, Guido. -----Original Message----- From: Lauer, Oliver [mailto:[EMAIL PROTECTED]] Sent: Monday, December 17, 2001 2:08 PM To: 'Tomcat Users List' Subject: AW: Classloader question Guido, I know that, that's what the classloader-how-to-do says, too, but in that case it was an application.jar that was put to web-inf and the classes weren't found either. > AXA eSolutions GmbH > AXA Konzern AG Germany > Oliver Lauer > Web Architect > Wörthstraße 34 > D-50668 Köln > Germany > Tel.: +49 221 148 31277 > Fax: +49 221 148 43963 > Mobil: +49 179 59 064 59 > e-Mail: [EMAIL PROTECTED] > _____________________________ > -----Ursprüngliche Nachricht----- Von: Guido Medina [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 17. Dezember 2001 19:03 An: 'Tomcat Users List' Betreff: RE: Classloader question Because WEB-INF/lib is for the specifique's application .jar files and WEB-INF/classes is for .class files, don't mix the concept, .jar files are treat as another kind of file system, that's why you put one in /lib and the second in /classes, and, for example if you want some driver for a database to be share through all the apps (JVMs) you put it inside TOMCAT_HOME/lib (if they are .jar) or in TOMCAT_HOME/classes (if they are .class), so, both directories have different purposes. I learned it with the experience and practice, Guido. -----Original Message----- From: Lauer, Oliver [mailto:[EMAIL PROTECTED]] Sent: Monday, December 17, 2001 1:57 PM To: 'Tomcat Users List' Subject: AW: Classloader question But why wasn't the class found in myapp/WEB-INF/lib ? Sorry, but I don't understand that !? > AXA eSolutions GmbH > AXA Konzern AG Germany > Oliver Lauer > Web Architect > Wörthstraße 34 > D-50668 Köln > Germany > Tel.: +49 221 148 31277 > Fax: +49 221 148 43963 > Mobil: +49 179 59 064 59 > e-Mail: [EMAIL PROTECTED] > _____________________________ > -----Ursprüngliche Nachricht----- Von: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 17. Dezember 2001 18:50 An: Tomcat Users List Betreff: Re: Classloader question On Mon, 17 Dec 2001, Heikki Doeleman wrote: > Date: Mon, 17 Dec 2001 13:06:21 +0100 > From: Heikki Doeleman <[EMAIL PROTECTED]> > Reply-To: Tomcat Users List <[EMAIL PROTECTED]> > To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> > Subject: Classloader question > > Hi everyone, > > trying to make a web application work using Tomcat 4.0.1 I found the > following behaviour, which I don't quite understand: > > my application uses a library called xhive.jar > > - putting xhive.jar in [catalina]/common/lib > This works fine, as expected > > > - putting it in [myapp]/WEB-INF/lib > Causes a ClassDefNotFoundError. I don't know why this is so, it does not > seem to conform to the description in class-loader-howto.html. However I did > see someone saying that in that directory, only .class files are added to > the classpath, not .jars > (http://www.geocrawler.com/archives/3/193/2000/12/0/4841079/). > > > - putting it in both those places > Causes a ClassCastException ?? Something seems to go terribly wrong when the > jar is placed in both those directories. > > Can anyone explain more about this? I'd like to know exactly how this works, > especially I'd like to know why classes from a jar in my application's > WEB-INF/lib apparently are not loaded. > This has been discussed numerous times in the archives, but the short answer is this: it is fundamental to the way Java class loaders work. The key issues: * A class named "a.b.c.Foo" loaded from two different class loaders is ***not*** the same class, even if the bytecodes are identical. Trying to assign from one to the other will give you ClassCastException errors. * The "new" operator in Java tries to load the specified class from the same classloader that loaded the class containing this code. If the class of that name has already been loaded by the "other" classloader, you again get ClassNotFoundException errors. * Class loader hierarchies can delegate "up" but not "down". Thus, it's also easy to have the "new" operator cause ClassNotFoundException errors, even though you "know" that the class is there. Moral of the story -- you are *always* best off having one and only one copy of a class visible to a web application. There's ways to deal with some of these issues, but they get pretty intricate. > Thanks > Heikki Doeleman > Craig McClanahan -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]> ---------------------------------------------------------------------------- -- Aus Rechts- und Sicherheitsgruenden ist die in dieser E-Mail gegebene Information nicht rechtsverbindlich. Eine rechtsverbindliche Bestaetigung reichen wir Ihnen gerne auf Anforderung in schriftlicher Form nach. Beachten Sie bitte, dass jede Form der unautorisierten Nutzung, Veroeffentlichung, Vervielfaeltigung oder Weitergabe des Inhalts dieser E-Mail nicht gestattet ist.Diese Nachricht ist ausschliesslich fuer den bezeichneten Adressaten oder dessen Vertreter bestimmt. Sollten Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertreter sein, so bitten wir Sie, sich mit dem Absender der E-Mail in Verbindung zu setzen. ---------------------------- For legal and security reasons the information provided in this e-mail is not legally binding. Upon request we would be pleased to provide you with a legally binding confirmation in written form. Any form of unauthorised use, publication, reproduction, copying or disclosure of the content of this e-mail is not permitted. This message is exclusively for the person addressed or their representative. If you are not the intended recipient of this message and its contents, please notify the sender immediately. ============================================================================ == -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]> ---------------------------------------------------------------------------- -- Aus Rechts- und Sicherheitsgruenden ist die in dieser E-Mail gegebene Information nicht rechtsverbindlich. Eine rechtsverbindliche Bestaetigung reichen wir Ihnen gerne auf Anforderung in schriftlicher Form nach. Beachten Sie bitte, dass jede Form der unautorisierten Nutzung, Veroeffentlichung, Vervielfaeltigung oder Weitergabe des Inhalts dieser E-Mail nicht gestattet ist.Diese Nachricht ist ausschliesslich fuer den bezeichneten Adressaten oder dessen Vertreter bestimmt. Sollten Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertreter sein, so bitten wir Sie, sich mit dem Absender der E-Mail in Verbindung zu setzen. ---------------------------- For legal and security reasons the information provided in this e-mail is not legally binding. Upon request we would be pleased to provide you with a legally binding confirmation in written form. Any form of unauthorised use, publication, reproduction, copying or disclosure of the content of this e-mail is not permitted. This message is exclusively for the person addressed or their representative. If you are not the intended recipient of this message and its contents, please notify the sender immediately. ============================================================================ == -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
