tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lee Crawford" <>
Subject Re: How can JSPs be part of an integrated component?
Date Sat, 30 Dec 2006 16:59:59 GMT
It's not the web.xml that's specific to Tomcat, it's the compiled JSP
classes (to be frank other JSP compilers might select totally different
filenames rendering the web.xml specific to Tomcat too).

Have a look at the .class files that are in the catalina-admin.jar. The
classes look like:

package admin;

public final class banner_jsp
  extends org.apache.jasper.runtime.HttpJspBase
   implements org.apache.jasper.runtime.JspSourceDependent
    private static java.util.Vector _jspx_dependants;
    private org.apache.jasper.runtime.TagHandlerPool

I'm going to have a look at what changes would be required to serve jsp's
directly from jars in the web-inf directory to solve my problem. Container
specific .war files doesn't seem the way to go.



On 12/30/06, Caldarale, Charles R <> wrote:
> > From: []
> > Subject: Re: How can JSPs be part of an integrated component?
> >
> > Sure, that works if you're banking on Tomcat as your
> > deployment target, but the classes that you've compiled
> > and hardwired (there many lines of hardwiring in the
> > admin web.xml) to Tomcat.
> None of what's in web.xml is specific to Tomcat - it's all defined by
> the servlet spec, and is usable on any container.  (What the admin app
> actually does is certainly specific to Tomcat, of course, but the
> pre-compilation mechanism is not.)  Compiling the JSP files into classes
> and generating the multitude of servlet mappings is normally done by an
> ANT script, of which there are numerous examples floating around.
> - Chuck
> MATERIAL and is thus for use only by the intended recipient. If you
> received this in error, please contact the sender and delete the e-mail
> and its attachments from all computers.
> ---------------------------------------------------------------------
> To start a new topic, e-mail:
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message