Hi Mel,
I noticed you used jakarta-tomcat/src/jasper34 for your protoype classes.
If you don't mind, I would like to move them in proposals/jasper34/xxxx,
and keep the work in jasper34 in the experimental area until it's ready.
I'll do a small commit - I did a refactoring for the runtime ( 1.1 so far,
I'm working on 1.2 ).
What I'm trying to do is:
- group the runtime components, make sure it has no dependencies on
compiler or other external classes
- identify a "ContainerLiaison" that will be implemented either in
JspServlet or in a container-specific class that will integrate jasper.
The runtime will be visible in the webapplication classpath ( either
provided by tomcat, or included in WEB-INF/lib if you want to use JspC and
deploy in a foreign, non-jasper-based container ).
This is a major change versus the previous model, where jasper used
directly some tomcat utils ( or cut&pasted utils in 4.0).
So far, the container services used by the runtime are:
- logging
- localization ( string manager )
- pools
A default implementation of the liaiason will use the current utils, but
we should be able to set the actual impl. at config time ( for example
set Log4J as logger, a special pool, etc ). The actual configuration will
be done by either JspServlet, or a container-specific module.
( the code generator is more complex, we need more discussions before
changing - I'll try to have something working as a start point )
Costin
( checkin probably this weekend )
