[jira] [Commented] (VELOCITY-975) Unicode characters cause issues
[
https://issues.apache.org/jira/browse/VELOCITY-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817935#comment-17817935
]
Alex O'Ree commented on VELOCITY-975:
-
striping it out before sending to velocity is a work around, but it's far from
ideal. It's hard to know what characters it will joke on. hmm, maybe i can rig
up a test to simple test all of the characters until a pattern emerges. I'm
working with content extract from an office document so there's absolutely no
guarantee that the character set can be entirely cleaned up.
Do you know what character set velocity is restricted to?
> Unicode characters cause issues
> ---
>
> Key: VELOCITY-975
> URL: https://issues.apache.org/jira/browse/VELOCITY-975
> Project: Velocity
> Issue Type: Bug
> Components: Engine
>Affects Versions: 2.3
>Reporter: Alex O'Ree
>Priority: Major
>
> Ran across some cases of processing files using velocity with some unicode
> characters in it that caused some unexpected results. Is there anything that
> I can do to prevent or mitigate this short of stripping out a set of bad
> characters before i had the script off to velocity?
>
> {noformat}
> org.apache.velocity.exception.ParseErrorException: Lexical error,
> Encountered: "\u00a0" (160), after : "" at *unset*[line 1, column 19]
> at
> org.apache.velocity.runtime.RuntimeInstance.evaluate(RuntimeInstance.java:1437)
> at
> org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:239)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
[jira] [Created] (VELOCITY-975) Unicode characters cause issues
Alex O'Ree created VELOCITY-975: --- Summary: Unicode characters cause issues Key: VELOCITY-975 URL: https://issues.apache.org/jira/browse/VELOCITY-975 Project: Velocity Issue Type: Bug Components: Engine Affects Versions: 2.3 Reporter: Alex O'Ree Ran across some cases of processing files using velocity with some unicode characters in it that caused some unexpected results. Is there anything that I can do to prevent or mitigate this short of stripping out a set of bad characters before i had the script off to velocity? org.apache.velocity.exception.ParseErrorException: Lexical error, Encountered: "\u00a0" (160), after : "" at *unset*[line 1, column 19] at org.apache.velocity.runtime.RuntimeInstance.evaluate(RuntimeInstance.java:1437) at org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:239) -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
[jira] [Created] (VELTOOLS-199) org.apache.velocity.tools.generic.ClassTool methods does not include inherited methods
Alex O'Ree created VELTOOLS-199: --- Summary: org.apache.velocity.tools.generic.ClassTool methods does not include inherited methods Key: VELTOOLS-199 URL: https://issues.apache.org/jira/browse/VELTOOLS-199 Project: Velocity Tools Issue Type: Bug Reporter: Alex O'Ree using tools 3.1 and using the class tool against a class that implements an interface and extends an abstract class. The class tools "methods" operation only returns methods directly implemented by the class and does not return any methods implemented by the abstract nor the interface. I'm not sure if this was on purpose, but it's pretty easy to get with reflection -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
