[
http://issues.apache.org/jira/browse/VELOCITY-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461862
]
Nathan Bubna commented on VELOCITY-504:
---------------------------------------
oops. i didn't finish that. it should've read "as a corollary to
VelocityEngine.evaluate()"
in other words:
#evaluate( ... ) is to VTL
as
engine.evaluate(...) is to Java
> Call to evaluate inside of macro fails with 1.5 beta2
> -----------------------------------------------------
>
> Key: VELOCITY-504
> URL: http://issues.apache.org/jira/browse/VELOCITY-504
> Project: Velocity
> Issue Type: Bug
> Components: Engine
> Affects Versions: 1.5 beta2
> Environment: Windows XP, Sun J2SE 1.5.0_09
> Reporter: Reggie Riser
> Assigned To: Henning Schmiedehausen
> Fix For: 1.5
>
> Attachments: evaltooltest.patch, macrotest.zip
>
>
> When upgrading from 1.5 beta 1 to beta2, I ran into a problem with one of our
> macros that makes a call to Velocity.evaluate (via a tool) within a foreach
> loop. With beta 1, everything worked fine. But we get a "cannot be
> resolved" error with beta 2. The same code works fine outside of a macro
> with either version.
> I've distilled the issue we're having down to a simple test case and have
> attached example code and a build file showing the problem. Just do an "ant
> beta1" or "ant beta2" to see how the results differ between beta1 and beta2.
--
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]
