Hi Greg, 

We are planning a small refactoring of jasper ( at least for tomcat3.3,
but one goal would be to merge the 2 branches we have in jakarta ). I
don't know when this will happen, but I know few people are looking
into that. 

Mel already made a proposal for improving JspServlet, and I will probably
make another one ( for the code generator and parser, plus extra
modularization ) as soon as I finish reviewing/fixing the 3.3 bugs.

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 ). 

It is not an easy project - and it would be great to get help, feedback
and sugestions from jetty developers. 

Costin





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
> 


Reply via email to