[ http://issues.apache.org/jira/browse/VELOCITY-432?page=comments#action_12370436 ]
Will Glass-Husain commented on VELOCITY-432: -------------------------------------------- Fixed the string out of bounds exception - thanks! (note - made minor code style adjustment) > #stop produces unexpected results when used with #parse > ------------------------------------------------------- > > Key: VELOCITY-432 > URL: http://issues.apache.org/jira/browse/VELOCITY-432 > Project: Velocity > Type: Bug > Components: Source > Versions: 1.4 > Reporter: Klemen Zagar > Priority: Minor > Fix For: 1.5 > Attachments: stop3-include.vm, stop3.vm, velocity-2006-01-20-1.patch, > velocity-2006-01-20-2.patch > > On 20th of January (2006) I took the latest trunk from SVN, and tried it > against some Velocity templates I am just working on. I came across two bugs, > which I am reporting here, along with patches: > 1. When #stop is issued from within #parse, the processing of subsequent > #parse directives does not stop. Since expressions are no longer being > rendered after a #stop, the parameter to #parse can be an empty string, > resulting in an unexpected exception that confuses the user. I am attaching > an example that reproduces this (stop3.vm, stop3-include.vm), with a patch > (-1.patch). > 2. I came across a string-out-of-bounds exception which happened because > string length was not being checked. Patch is attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
