> <pulp>
> > Command line usage:
> > Step1 - 280ms
> > Step2 - 20ms
> > Step3 - 3946ms
> > Step4 - 531ms
> >
> > Servlet in Tomcat 3.2.1
> > Step1 - 2954ms
> > Step2 - 421ms
> > Step3 - 46266ms
> > Step4 - 8442ms
> >
> > As you can see, the performance degraded by about 10 times. I got around
> > this by going against everything I believed about where to place libs in
> > tomcat and loaded all jars in the server startup script. The problem goes
> > away.
> >
> > I believe this is a problem with class loading on Tomcat.
> </pulp>
It may be - that's why we have 3.3 :-) Xalan, xerces, are loading a lot of
classes - but this is only startup time.
Thanks to Nacho, most of the class loading problems are resolved
( well, I also had a small contribution, so did Henri and Larry :-) - and
it seems the loading speed is pretty good now.
Unfortunately it's very hard ( and dangerous ) to port the changes to
3.2.x.
Tomcat 3.3 uses only URLClassLoader - if JDK1.2 is detected - and only
"standard" parent delegation. I tested it with xerces, jaxp1.1, etc - it
all seems to work.
The only problem is that by default, no parser is provided to applications
- I'm working on a solution that will allow the admin to specify that an
application needs a parser ( and what parser to provide by default ).
( in other words - to define different "profiles" - the default will
probably remain the most conservative - no library provided by the
container )
Costin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
