Hello,
another (two) remarks:
If I include JSPs into a velocity based template system, I get (nothing
else changed) the exception java.lang.IllegalStateException:
getOutputStream() has already been called for this response.
This may be because data.getResponse().getOutputStream() is already
called from the velocity handlers (VelocityDirectScreen,... calling
org.apache.turbine.services.velocity.TurbineVelocity.handleRequest
(Context, String, OutputStream).
Only if I use an buffered version of the response
(org.apache.jetspeed.services.jsp.HttpBufferedResponse.HttpBufferedResponse
(HttpServletResponse, PrintWriter)) the exception
java.lang.IllegalStateException is not thrown.
The next problem is that in
org.apache.turbine.services.jsp.TurbineJspService.handleRequest(RunData,
String, boolean) the variable relativeTemplateName has its leading
slashes (if any) removed. But this leads to an IllegalArgumentException
from org.apache.catalina.core.ApplicationContext.getRequestDispatcher,
which requires a leading slash. If relativeTemplateName has its leading
slash again reset the response is successfull.
May be this is a bug.
With this two changes applied I could indeed load the JSPs.
Best regards,
Georg
Von: Thomas Vandahl <[email protected]>
An: Turbine Developers List <[email protected]>, Turbine Users
List <[email protected]>
Datum: 28.08.2011 12:35
Betreff: Turbine 4.0 Migration Guide
Hi folks,
I started to fill up the Migration Guide for upgrading a Turbine 2.3.3
application to Turbine 4.0M1. See the Turbine Wiki at
http://wiki.apache.org/turbine/Turbine4/Turbine4.0M1/Migrate233
I would like to invite everyone to add your own experiences to the page.
Feedback to the topics already covered is also very welcome.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
