Thank you very much: That was exactly the information I was looking for.
Regards,
Henning
-----Original Message-----
From: Larry Isaacs [mailto:[EMAIL PROTECTED]]
Sent: Montag, 12. März 2001 15:12
To: '[EMAIL PROTECTED]'
Subject: RE: class loader separation of API and implementation in tomcat
This is being addressed in Tomcat 3.3. Nightly builds of Tomcat 3.3
are curretly broken, but should be back soon. Soon afterwards
Tomcat 3.3 Milestone 2 should occur. You can take a look at
either of these (once available) to see what is coming.
While you are waiting, here is what is in the readme file that
addresses this:
Tomcat 3.3m2 now uses a new hierarchy of class loaders. It provides
for the separation of the classes used by the Tomcat container and
the classes used by web applications. This solves a major problem
in Tomcat 3.2 where all web applications had to share Tomcat's XML
parser. Now each web applicaton can have its own XML parser, or if
desired all web applications can share an XML parser different from
the one used by Tomcat. As a side effect of this change, web
applications in Tomcat 3.3m2 are not provided an XML parser by
default. You must supply one if your web application requires one.
For details about where to place jar files, see the README files in
the "lib/container", "lib/common", and "lib/apps" directories of your
Tomcat installation.
Cheers,
Larry
> -----Original Message-----
> From: Blohm, Henning [mailto:[EMAIL PROTECTED]]
> Sent: Monday, March 12, 2001 4:08 AM
> To: [EMAIL PROTECTED]
> Subject: class loader separation of API and implementation in tomcat
>
>
> Hi everybody,
> I had a problem with the tomcat 3.1 release that I hoped
> would be resolved
> by newer releases, but it seems that that never happened:
> Since tomcat is a framework that integrates Java code it
> seems natural that
> tomcat should have a class loader hierarchy that cleanly separates the
> tomcat implementation classes from the API, so that there is no class
> collisions between classes used by an application and by
> tomcat itself.
> Although tomcat seems to follow that principle when loading
> servlets, it
> doesn't apply it to itself. Just yesterday, I downloaded the
> 3.2.1 release
> and it seems that you still have to put parser.jar and
> jaxp.jar from the
> tomcat's lib folder into the main classpath which effectively
> prohibites the
> use of other xml libraries (with the same class names but different
> implementations) in servlets.
> Is this really true? Is there a way to configure tomcat so
> that you do not
> have to worry about any classes the tomcat implementation loads?
> For a production environment that must be able to accept any
> web application
> as long as it complies to the servlet API, this behaviour
> seems unacceptable
> to me...
> Does anybody know of a solution?
> Thank you!
> Henning
> Ps: Nevertheless, I think tomcat is truly a great open source project!
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
