"Ignacio J. Ortega" wrote:
> >
> >
> > 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???
> >
>
> I think Craig has done it in CVS , pick a nightly build or from CVS,
> hopefully it will be solved.., basic
Stuart Thomson wrote:
> "Craig R. McClanahan" wrote:
> >
> > Stuart Thomson wrote:
> >
> > > > 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" dire
>
> 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...
>
ssage -
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 setti
"Craig R. McClanahan" wrote:
>
> Stuart Thomson wrote:
>
> > > 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 Tom
Stuart Thomson wrote:
> > 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.
GOMEZ Henri wrote:
>
> >> This will probably stop me from ever going to Tomcat 3.3. Finding
> >> classes on the classpath is very convenient at development time.
> >>
>
> >Your opinion is took into account for the 3.3 release..
>
> Sure, we could still have a flag -keepcp to tomcat.sh/tomcat.
"Ignacio J. Ortega" wrote:
>
> > > 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"
> >
>> This will probably stop me from ever going to Tomcat 3.3. Finding
>> classes on the classpath is very convenient at development time.
>>
>Your opinion is took into account for the 3.3 release..
Sure, we could still have a flag -keepcp to tomcat.sh/tomcat.bat.
But take a look also at Tomcat
> > 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
> 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 fro
The first milestone release of the next version of Tomcat 3.x is available
for download and testing. As a Tomcat 3.x release, it remains an
implementation of the Servlet 2.2 and JSP 1.1 specifications.
In addition to bug fixes, a large amount of refactoring has gone into
Tomcat 3.3m1 since Tomca
12 matches
Mail list logo
