[OT] are tomcat and jetty simply alternative java servlet engines?
Robert P. J. Day
rpjday at crashcourse.ca
Thu Jun 24 20:11:47 UTC 2010
On Thu, 24 Jun 2010, Carlos A. Carnero Delgado wrote:
> On 6/24/10, Robert P. J. Day <rpjday at crashcourse.ca> wrote:
> > yes, it's OT, but i suspect someone here can answer this in one
> > sentence or less. i've downloaded a package that permits building
> > selecting either tomcat or jetty, so i just want to clarify that those
> > two packages are simply alternative java servlet engines.
> Yup, you're 100% correct, Both are servlet containers.
> > and, as a last point, both of the above are just lighter
> > alternatives to a full-figured jboss install, is that correct?
> Yes, again. They provide only the servlet technology* whereas a full
> blow JEE container such as JBoss or Glassfish go for the whole JEE
> *Well, actually they (Tomcat & Jetty) support other pieces, JSP, JNDI,
> etc. but not EJB, for instance.
that's about what i thought -- it means that if someone presents an
app that requires a java servlet engine, it's possible they'll have
three different versions of that app -- one each for jboss, tomcat and
jetty, is that correct?
or let me ask that another way -- when you build such an app, does
it have to know which java servlet engine you'll be running it
Robert P. J. Day Waterloo, Ontario, CANADA
Top-notch, inexpensive online Linux/OSS/kernel courses
More information about the ubuntu-users