Hola Raphael :
> 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
This is a continuos requeriment from Tomcat users :(, and a logical one,
and in addtion it's far more easy to implement in this way than the 2.2
way, but the specs are painful at times.., i'm trying already to get to
understand what the spec architect have in mind putting that
restriction.... :(
> something to make the EcsServletElement work with Velocity on
> Tomcat 3.x
> but the JSP screens work OK.
>
What do you need?, i do not follow very closely discussions here if
this have been disscussed in past , sorry, but a brief explanation can
help people to get know what you are trying to achieve, and see if
anybody can help you.
> Can anybody confirm whether this breaks Jetspeed operation in other
> servlet 2.2 containers ?
> If it does, I'll rollback the changes.
>
I dont know, but i can imagine any Servlet 2.2 Container will ignore a
subclassed request, if it's compliant at least.., but if some jetspeed
functionality relies on this subclassing to work , i can imagine this
functionality is broken at least on Servlet 2.2 Containers..
I'm here to stay for a time, i'm interested on any problem you have
running on Tomcat 3.3, if you use it..and on JetSpeed itself, for now
it's down on my priorities list, but who knows...
FYI: JetSpeed runs like a charm on Tomcat 3.3 and runs much faster ( by
a factor of 2 or so ) than in 3.2...:)
Saludos ,
Ignacio J. Ortega
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/jetspeed@list.working-dogs.com/>
List Help?: [EMAIL PROTECTED]
