[
https://issues.apache.org/jira/browse/VELTOOLS-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELTOOLS-160.
-------------------------------------
Resolution: Fixed
Assignee: Claude Brisson
Fix Version/s: 3.0
XmlTool now uses standard JDK XML parsers instead of dom4j, and doesn't seem to
suffer from this problem.
> XmlTool: possibility to add NamespaceContext for XPath (find method)
> ---------------------------------------------------------------------
>
> Key: VELTOOLS-160
> URL: https://issues.apache.org/jira/browse/VELTOOLS-160
> Project: Velocity Tools
> Issue Type: Improvement
> Components: GenericTools
> Affects Versions: 2.0
> Reporter: steven van vlierberghe
> Assignee: Claude Brisson
> Priority: Major
> Labels: features
> Fix For: 3.0
>
>
> I inject in the Velocity context xmlf1 as an XmlTool instance corresponding
> with some user-defined input file. This allows the user to build the Velocity
> template using constructs like $xmlf1.OrderId and so on.
> This works great if the input xml does not contain namespaces.
> Otherwise, he has to write
> $xmlf1.find('//*[local-name()="OrderId"]/text()') which is much more complex.
> Can I pass-through some NamespaceContext instance to the XmlTool instance
> that I make available, so that a plain $xmlf1.OrderId also works ?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
