[
https://issues.apache.org/jira/browse/VELOCITY-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-796.
-----------------------------------
Resolution: Duplicate
It's definitely not #parse that's the problem, if some of the content is
parsed. And since it's a spotty occurence and your screenshot shows that all
the "unparsed" output is macro calls, Sergiu is right on. It's a race
condition in the local macro namespace. See VELOCITY-776 for full explanation
and the options available to you for working around it until we get a proper
fix.
> Velocity #parse not parsing content.
> ------------------------------------
>
> Key: VELOCITY-796
> URL: https://issues.apache.org/jira/browse/VELOCITY-796
> Project: Velocity
> Issue Type: Bug
> Components: Engine
> Affects Versions: 1.7
> Environment: Linux Server running Apache Web Server in front of a
> JBoss 5 Application Server
> Reporter: Wayne Baskin
> Attachments: Velocity Screen Shot.jpg, viewer.png
>
>
> The issue is occuring randomly and could be load related.
> The issue has only appeared since upgrading to Version 1.7.
> The parse element will display all Velccity code it was suppose to parse.
> I have a screen shot if required.
--
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]
