Costin,
[EMAIL PROTECTED] wrote:
>...
> The end result will be a more portable jasper - that will be usable in
> multiple containers with minimal pain ( and with enough hooks to allow the
> container to provide specific features and optimizations ).
Excellent - That sounds much easier for us to keep in sync with.
Still, it would be good to have a maintainer to step forward and help
us with the transition.... It may be good for somebody on the development
team to have another servlet container to test against?
> It is not an easy project - and it would be great to get help, feedback
> and sugestions from jetty developers.
Ok - I'll give brief over view of the changes and ideas that we have at the
moment.
The first change we made was to provide a logging facade class, so that the
link with tomcat logging could be broken. Jasper code makes logging calls
on a Jasper class, which we have implemented to call the Jetty logging
facility. This probably should be generalized so that a dynamically
selected logging facade can be configured for JSP.
Secondly we replaced the XML parsing with our own wrappers for a JAXP
parser. As Jetty is targetted for small memory footprint systems, we
wish to avoid DOM as it is too heavy weight when you consider it is often
only used only to read a config file (once loaded, the DOM classes stay
in memory). I think a generic jasper should probably only assume a JAXP
parser in the environment and then only use the SAX elements of it.
Another concern I have is that I don't think that jasper should be parsing
the web.xml file itself. Consider an deployment in an EJB container that
uses JSP, the web.xml may be parsed 3 times, once by the EJB container looking
for ejb-ref tags, once by the servlet container and then finally by the
JspServlet. I think Jasper should be written to allow a deployer to push
this configuration into it. Initially it would have to have it's own pusher that
did parse the web.xml file, but eventually it would be good to make a proposal
to the servlet spec guys to come up with an API to allow a servlet container
to export the parts of the web.xml it does not know how to handle.
For example - the jetty/jboss integration module under development now registers
for callbacks when the container parses ejb-ref tags.
The classloading configuration is a bit ugly. I'm not sure how this
can be cleaned up, but currently in Jetty we have hard coded detection of the
JspServlet so that the context classloader can be set as an InitParam. It
would be better jasper could do a better job of trying to locate the context
classloader itself.
Finally I also have a few half formed ideas of how to improve the generation of
web.xml fragments by the pre-compiler, so that it pays better attention
to existing jsp mappings in the existing web.xml.
Is there a jasper specific mailing list that we can tune into to monitor
your jasper efforts? or is it just the general tomcat dev mailing list?
If nobody steps forward to help maintain jetty-jasper (I call it jesper :-)
and transition to the new portable version, then it would be good to have
a focused mailing list to monitor and contribute to.
And just to end on a positive note... our users that have switched from our
older versions to our jasper based version have reported positive
feedback with regards to performance and stability.
regards
>
> On Mon, 9 Apr 2001, Greg Wilkins wrote:
>
>
>> The Jetty project is in need of a Jasper maintainer for it's cut of the
>> Jasper JSP engine.
>>
>> Jetty is a opensource java HTTP server and servlet container (see
>http://jetty.mortbay.com
>> or http://sourceforge.net/projects/jetty) It is intended to be small, fast, yet
>fully functional.
>>
>> For JSP handling, we have taken a branch of the jasper code. The branch was
>required
>> as we need to decouple the logging and XML parsing from tomcat. However, this
>branch
>> is now a little bit of an orphan and requires a maintainer to :
>>
>> + Keep it up to date with the latest jasper development.
>>
>> + Cleanup the current jetty integration - specially with regards to
>> classloading, logging and XML parsing.
>>
>> + Feedback changes and suggestions that may make jasper more portable
>> between servlet containers (this may require removal of Jetty dependancies
>> that were added in place of tomcat ones).
>>
>> + Testing of the integration using watchdog.
>>
>> + Planning and executing the upgrade of Jetty from servlet 2.2 and JSP1.1 to
>> 2.3/1.2.
>>
>> Anybody who can help with some or all of this will be warmly welcomed to the
>> Jetty project.
>>
>> I'm not subscribed to tomcat-dev, so can responses be directed to
>> [EMAIL PROTECTED] or [EMAIL PROTECTED]
>>
>> regards
>>
>
>
>
>
> ------------------------ Yahoo! Groups Sponsor ---------------------~-~>
> Secure your servers with 128-bit SSL encryption!
> Grab your copy of VeriSign's FREE Guide,
> "Securing Your Web site for Business." Get it now!
> http://us.click.yahoo.com/KVNB7A/e.WCAA/bT0EAA/CxaWlB/TM
> ---------------------------------------------------------------------_->
>
> For the latest information about Jetty, please see http://jetty.mortbay.
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
