You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Christian Mallwitz <c....@intershop.de> on 2000/12/21 15:34:59 UTC
How to do my own JSP processing
Hi,
I want to write a servlet that reads JSP files from somewhere outside the
servlets web application context, compiles them to a location outside the
servlets web application (if necessary) and then invokes the compiled
servlet class.
I started looking at org.apache.jasper.servlet.JspServlet for a start but it
looks really messy. Besides the Jasper classes lack some documentation to
put it mildly ... :-)
What should I really look at and what things do I have to look out for?
The result should work similar to using request dispatchers include() but
with more control over it (especially response header generation, response
buffering, etc.) Tag lib stuff should work seemless in all the pages.
Thanks
Christian
--
Christian Mallwitz INTERSHOP Communications Germany
Senior Software Engineer phone: +49 3641 50 3453
Re: How to do my own JSP processing
Posted by "Craig R. McClanahan" <Cr...@eng.sun.com>.
Christian Mallwitz wrote:
> Hi,
>
> I want to write a servlet that reads JSP files from somewhere outside the
> servlets web application context, compiles them to a location outside the
> servlets web application (if necessary) and then invokes the compiled
> servlet class.
>
> I started looking at org.apache.jasper.servlet.JspServlet for a start but it
> looks really messy. Besides the Jasper classes lack some documentation to
> put it mildly ... :-)
>
> What should I really look at and what things do I have to look out for?
>
> The result should work similar to using request dispatchers include() but
> with more control over it (especially response header generation, response
> buffering, etc.) Tag lib stuff should work seemless in all the pages.
>
Sounds like you are planning on inventing your own variant of a servlet+JSP
server, since you're wanting to change or ignore many of the spec requirements.
And you will end up with an app that will only run in your own server. Unless
you like building servers as a hobby, you've got a *lot* of hard work ahead of
you.
I would suggest you look at how you can architect your application *within* the
requirements of the servlet and JSP specs. That way, you can focus on writing
an app rather than a server, and have some assurance that you can run that app
elsewhere if and when you outgrow Tomcat.
>
> Thanks
> Christian
> --
> Christian Mallwitz INTERSHOP Communications Germany
> Senior Software Engineer phone: +49 3641 50 3453
Craig McClanahan