[VELTOOLS-7] Add the VelocityWriter to the context of the VelocityViewServlet

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.1
• Fix Version/s: 1.2
• Environment: Operating System: All; Platform: All
• Bugzilla Id: 9139
• Assignee: Nathan Bubna
• Reporter: Bill Boland
• Created: 16/May/02 08:04
• Updated: 25/Jan/07 05:44
• Resolved: 15/Oct/05 07:16

Description

The reason and purpose of this is for performance situations as stated by
[e-mail]

Following the recent thread discussion...

http://www.mail-archive.com/[e-mail]/msg07051.html
http://www.mail-archive.com/[e-mail]/msg07066.html

<snip>
BUT...this shows where an enhancement would be nice to have. If the
statement in the mergeTemplate() method of:

template.merge( context, vw);

was replaced with:

performMerge( template, context, vm );

where performMerge was a protected method of VelocityServlet with the
original statement as its default behavior, then you could easily
override this method in a subclass of VelocityServlet to place the
writer into the context. The VelocityServlet could still manage the
private writerPool.
<\snip>

An alternative solution would be to allow the writerPool, encoding and other
private methods be protected so that it would be easier to override the
mergerTemplate method so this could be implemented by the developer. Maybe both
should be done.

bill