[ https://issues.apache.org/jira/browse/VELOCITY-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claude Brisson resolved VELOCITY-437. ------------------------------------- Resolution: Fixed Fix Version/s: 1.6 By the way, isn't this interface everything you need to do what you want, that is have templates associated with client objects, and be able to re-use the main writer? I'm not sure you'd need some other interception mechanism. The ValueWriter stuff looks really too heavy to me. So I'm resolving this issue - but feel free to reopen it afterwards otherwise. > Intercept output of objects > --------------------------- > > Key: VELOCITY-437 > URL: https://issues.apache.org/jira/browse/VELOCITY-437 > Project: Velocity > Issue Type: New Feature > Components: Engine > Affects Versions: 1.4 > Reporter: Ståle Undheim > Priority: Minor > Fix For: 1.6 > > Attachments: valuewriter.patch > > > Currently, all reference objects in a Velocity template file are put out > using the objects toString method, with no means to control this mechanism. I > propose to change this by having interceptors that can pick up variables > before they are run .toString on, and write them using their own means > instead. > If I figure out how to attach files to this after posting, I will add a patch > with all the code necessary to implement this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]