One thing related to this but not to Tomcat 3.3. I'm using Xerces and Xalan
and I have to place the Xerces and Xalan jars in the tomcat.sh/bat classpath
because Xerces has newer org.w3c.dom stuff in it. The old Tomcat 3.2.1 XML
stuff (w3c.jar) misses some methods and stuff...
This must be a well-known thing. I always thought the adaptive classloader
would keep up different namespaces for me so the Tomcat system classloader
doesn't interfere with the classloader of any webapp. But that doesn't seem
to work. So now each time I'm deploying a webapplication that uses Xerces or
Xalan I'll have to modify the tomcat.sh/bat. This is one thing I don't
really like because I'm delivering a development CD with a .war file on it
for deployment in any servlet environment. This one isn't just deployable,
nooo you'll have to modify the .sh file...
That's somehow kind of fucked. Does anyone have a solution for this or does
it get any better in 3.3????
Then the last problem. I tried to use Cocoon under tomcat 4b and it wouldn't
work because of a sealing violation... Known to u guys???
Thnx in advance,
Alef Arendsen
----- Original Message -----
From: "Ignacio J. Ortega" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, February 17, 2001 16:36
Subject: RE: [ANNOUNCEMENT] Tomcat 3.3 Milestone 1
> > > 3) The new class loader scheme in this release ignores your
> > CLASSPATH setting.
> > > Instead, you are expected to add needed jars to Tomcat's
> > "lib", "lib/common",
> > > and "lib/shared" directories. See the "README" file in
> > Tomcat's "doc"
> > > directory for details.
> >
> > This will probably stop me from ever going to Tomcat 3.3. Finding
> > classes on the classpath is very convenient at development time.
> >
>
>
> Well not that hard, Tomcat 3.3 by itself dont tries to respect your
> classpath, but because the tomcat.(sh|bat) simply cleans classpath env
> var before starting ( and recall it when it ends ) tomcat.., but by
> itself dont takes any internal measure to do so, you can i.e construct a
> classpath and modify tomcat.(sh|bat) shell command to start command with
> a classpath of your own...
>
> The thinking was "if you are someone that knows to have a classpath you
> will knows too how modify tomcat.{sh|bat) to use it" to alleviate low
> end user problems when first using Tomcat 3.3.
>
> Your opinion is took into account for the 3.3 release..
>
> Thanks for the feedback.
>
> Saludos ,
> Ignacio J. Ortega
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
