> > but it's worth mentioning that the main branch of
> > "jakarta-tomcat" (where you committed your change for build.xml) is the
> > "3.3" development tree.
> >
> > If, on the other hand, you want to use the 3.2 branch that I'm preparing
> > for release, you will want to check out branch "tomcat_32" from the
> > "jakarta-tomcat" repository.
>
> ug...ok...i will do that...i didn't realize.
>
> -jon (who isn't real thrilled with the current tomcat development style
> going on in the jakarta-tomcat tree)
Which tree ? And what's the complaint ? If you read the archives and the
cvs logs I think everything was explained and so far I haven't saw any -1.
( at least for the 3.3 development branch ).
If you want to contribute - wellcome, any sugestion and idea is good !
Regarding the facade22.jar - I will remove the second copy ( in
lib/servlet22 ) - since we all agreed the servlet2.3 facade will be part
of a future revolution ( when 3.3 will be stable and all other things will
be resolved ).
If the question was "what it is " - it's the implementation of the 2.2
servlet API. It is built in a separate jar in order to make sure the
layers are separated and remain separated, avoiding "convoluted" code. The
"facade" pattern is part of tomcat design and provides many advantages (
I think it's documented ), and 3.3 will be the first that will (finally
) implement it right ( 3.2 still has many interdependencies between
layers).
Costin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
