On Wed, 19 Dec 2001, David Morsberger wrote:
> Date: Wed, 19 Dec 2001 21:19:16 -0500
> From: David Morsberger <[EMAIL PROTECTED]>
> Reply-To: Tomcat Users List <[EMAIL PROTECTED]>
> To: Tomcat Users List <[EMAIL PROTECTED]>,
> "Lauer, Oliver" <[EMAIL PROTECTED]>
> Subject: Re: AW: Classloader question
>
> I ran into a similar problem today that I can not explain while upgrading to
> tomcat 3.3. The JSP we created accesses a bean that uses the oracle 1.2 JDBC
> driver, classes12.zip.
>
> I placed the Oracle classes12.zip file in the myapp/WEB-INF/lib directory
> and then I got the NoClassDef exception.
>
This is the expected behavior.
> I unjar'd the .zip file in the myapp/WEB-INF/lib directory and still got the
> NoClassDef exception.
>
So is this.
> I unjar'd the .zip file in the myapp/WEB-INF/classes directory and it
> worked.
>
And this. As an alternative, if you had put the JDBC driver in a JAR file
in the /WEB-INF/lib directory, it also would have worked.
See the Servlet Specification for more details about where web
applications load classes from (unpacked classes under /WEB-INF/classes or
***JAR FILES*** under /WEB-INF/lib).
> Where should the .zip file be placed for inclusion in a bean? I recycled
> Tomcat after every attempt.
Nowhere.
Servlet containers look for JAR files, not ZIP files. Why Oracle persists
in shipping their JDBC drivers in ZIP format is a mystery to me -- but the
complaints should go to them.
Craig McClanahan
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
