[TRB-85] Nested Templates output reversed

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Core 4.0-M1
• Fix Version/s: Core 4.0-M2
• Component/s: Core
• Environment: Windows XP, ; java version "1.6.0_13"; Java(TM) SE Runtime Environment (build 1.6.0_13-b03); Java HotSpot(TM) Server VM (build 11.3-b02, mixed mode); Tomcat 6.0.18_03
• Assignee: Georg Kallidis
• Reporter: Georg Kallidis
• Created: 08/Sep/11 10:12
• Updated: 01/Feb/13 15:45
• Resolved: 01/Feb/13 15:45

Description

Using (nested) calls in screen template the output (of the templates) seems to be reversed, i.e. the latest called templates are outputted first (lifo).
This may be due to that org.apache.turbine.services.velocity.TurbineVelocityService.handleRequest(Context, String) is implemented such, that each invocation creates a new instance of a java.io.OutputStreamWriter.OutputStreamWriter(OutputStream, String), which velocity then is writing to. May be the exact reason should be investigated in more detail. No test is available at the moment.

This could be solved by providing a concurrent safe instance variable of OutputStreamWriter to be used in this method (handleRequest).

Cft. http://mail-archives.apache.org/mod_mbox/turbine-dev/201109.mbox/[e-mail]%3E

A patch could be attached later ..