"Ignacio J. Ortega" wrote:
>
> Hola Raphael:
>
> > + // Include the servlet or JSP.
> > +
> > + // Warning: This does not work correctly with Tomcat
> 3.x
> > + // because of a Tomcat implmentation bug (the
> dispatcher
> > + // never use the given response)
> > + dispatcher.include(
> > + rundata.getRequest(),
> > + new
> > EcsServletResponse(rundata.getResponse(),out) );
>
> This is not true, Servlet 2.2 requires that the response and request
> object pased to a included servlet be the same passed to the including
> servlet, dont blame on Tomcat 3.X, blame on Sun Specs, this not a bug at
> all... not in 3.X at least, as they are Servlet 2.2 Containers...
>
I didn't know this.
> Doing this change you have tied JetSpeed to Servlet 2.3 Containers,
> that's not bad at all , if Servlet 2.3 Spec were final , but in this
> moment you only blocking yourself to non released versions of
> Specifications, very bad for a truly compatible webapp, take care..
>
> For me ( and a bunch of others who wait for specs to be finals to use
> them.., i know many people already tied to Tomcat 3.1 :) this is a ver
> bad change.. we are not ready to change our Oracle Servers to Servlet
> 2.3 in a near future, so JetSpeed is not for us ?
>
I committed this, because on Tomcat 3.x the behavior is exactly the same
as before (and thus the patch does not break or solve anything since
Tomcat 3.x just ignores my custom response). I'll still have to find
something to make the EcsServletElement work with Velocity on Tomcat 3.x
but the JSP screens work OK.
Can anybody confirm whether this breaks Jetspeed operation in other
servlet 2.2 containers ?
If it does, I'll rollback the changes.
--
Raphaël Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Services Manager / Paris
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/jetspeed@list.working-dogs.com/>
List Help?: [EMAIL PROTECTED]
