> In any case, setResponse() looks dangerous. For instance, we have a portlet in
>Jetspeed that can display
> a Turbine screen in a window. This is, obviously, if the screen does not call
>setResponse().
>
> Having this method public looks dangerous to me.
>
> Is there a good reason to change the HTTP response outside of the "core" turbine
>code?
>
Yes, I think you are right. I found another way to do what I
needed to do without setting the servlet response. All is well :-)
jvz.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
