RE: [WEB400] New System Development Tomcat Tuning

["David Morris" <David.Morris@xxxxxxxxxxxxx>]

Tim,

By using the 1.3 JDK and playing around with the memory allocated to
the JVM and garbage collection, I bet Joe could have improved on this.


Because Tomcat is the reference platform for the JSP and Servlet
specifications, the question is backwards. It should be "Is there
anything
that WebSphere can't do that Tomcat does?" The answer is that
WebSphere does not follow the standards exactly, which may cause
problems with some servlets. Tomcat 4.0 is also based on the Servlet
2.3 specification with adds filters, which are very important and will

likely change the way people write servlets. Filters allow you to pipe

output from one process to another. For example, you might generate
an XML document and then use a filter to transform that to HTML.

Tomcat cannot run EJBs without some other help like JBOSS or Enhydra.
I really don't know why someone would want to use EJBs unless you have

a highly distributed application model. There are lightweight
persistence
mechanisms available that are simpler and fit between full blown EJBs
and naked servlets that can help with the database persistence that
are worth looking at if you really think you need EJBs.

David Morris

>>> thatzenbeler@clinitech.net 05/13/02 10:10AM >>>
This message is in MIME format. Since your mail reader does not
understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Thanks running the tests... It's nice to know, that Tomcat can run at
the
same speeds...

So with that being said, is their any functionality difference between
Tomcat and the standard WebSphere?

Is there anything Tomcat can't do, when it comes to running the web
apps?

thanks, tim