"Craig R. McClanahan" wrote:
> [...]
> If it is Tomcat-specific, is there any reason it really needs to be a separate
> Jakarta project at all? Why not just absorb it into Tomcat?
>
> In terms of CVS repositories, if the amount of version-dependent code is large it
> would be easier just to put it in the existing version repositories as an
> optional feature. If it's mostly independent with just a few links, a separate
> CVS repository, under the auspices of the Tomcat project, seems to be much more
> straightforward.
There are a few reasons I suggested a separate Jakarta project:
1) Since it's optional, not part of the Servlet spec, and most likely
of interest to less than the majority, keeping it in the main TC
project just adds overhead (larger downloads, more to build, etc.)
2) Initially, it only supports TC 3.2. But 3.2 is in bugfix mode, so
adding this as a new module (feature) in 3.2.1 doesn't seem right.
3) Except for a small amount of code that's needed to tie into the
servlet container, it's independent from the various containers.
I have not made any attempts to refactor the code yet, but the
container interface could be a very simple class. It would then be easy
to add interfaces to non-Tomcat containers as well. Keeping it as a
separate project means that all improvements automatically applies
to all supported containers.
Hans
--
Hans Bergsten [EMAIL PROTECTED]
Gefion Software http://www.gefionsoftware.com
Author of JavaServer Pages (O'Reilly), http://TheJSPBook.com
