On 30.08.11 09:47, Georg Kallidis wrote: > http://wiki.apache.org/turbine/Turbine2/VelocityOnlyLayout getting the > error java.lang.IllegalStateException: getOutputStream() has already > been called for this response. [...] > Doing this the problem seems to be resolved.
I think I got it now. The problem is that multiple calls to data.getResponse().getOutputStream() happen at different places in Turbine while getOut() was cached before. This makes me wonder how this was meant to work in the first place. I appreciate the fix for TurbineVelocityService. From what I understand, however, this might lead to confusion between output streams when multiple requests are being handled concurrently. Which brings us back to the first question: How this was meant to work without caching in the first place? Is anyone of the more experienced people able to shed some light on this? > I get another error, if I have in the default > turbine-classic-pipeline.xml > > <org.apache.turbine.pipeline.DetermineRedirectRequestedValve/>: [...] > The reason are, that two deprecated variables have their default > value ?? Yeah, right you are. This comparison is obviously wrong when the RunData methods are being by-passed. Right now, I don't have an idea how to solve this. Thanks for your contribution. I didn't know that Turbine 2.3.3 would run with JetSpeed at all. I wrote a JSR-286-Portlet bridge for Turbine to be used in Liferay. Maybe we can share some experiences? Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
