[
https://issues.apache.org/jira/browse/VELOCITY-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559850#action_12559850
]
Guido Deinhammer commented on VELOCITY-454:
-------------------------------------------
In Addition to the problems above there seems to be no way to escape a plain \
- trying the obvious \\ results in... \\ in the output data. and using just a
single \ anywhere in the template results in a parsing error. This is quite
annoying with hardly a useful workaround...other than assigning "\\" to a
variable, cutting off the second character and using a variable instead of \
In the context of this ticket this should also be addressed.
> clean up escaping to always escape \$ and \#
> --------------------------------------------
>
> Key: VELOCITY-454
> URL: https://issues.apache.org/jira/browse/VELOCITY-454
> Project: Velocity
> Issue Type: Improvement
> Components: Engine
> Affects Versions: 1.4, 1.5
> Reporter: Bjoern Guenzel
> Fix For: 1.6, 2.0
>
> Attachments: testVelocity.vm
>
>
> I want to use Velocity to generate a template for UJAC, which uses a very
> similiar templating language to Velocity. Therefore escaping is a primary
> concern.
> I am surprised that there seems to be no way to just escape "$" and "#" in
> general.
> Suppose we have the line \$name
> If name is in the context, this will evaluate to $name, otherwise it will
> evaluate to \$name
> The real problem starts if there is something to escaped like
> ${something == 3} (this is something that might occur in a UJAC template)
> This gives an error in both cases: ${something == 3} and \${something == 3}
> both give an error ("} expected" or something like that).
> My guess is that Velocity get's confused when trying to evaluate "something
> == 3" to see if it is something that is known and should be escaped or
> something that is unknown and should not be escaped.
> In my opinion the proper behaviour for escaping characters would be to ALWAYS
> escape, independent of the context.
> Even if the current way of escaping would work in all cases, there would be a
> major problem with it. I can't give the velocity template to the Designer,
> because only the developer knows all the variables that exist in the context.
> So the designer is unable to properly escape all the variables. I think it
> would be important to have a way to simply escape everything.
--
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]
