[
https://issues.apache.org/jira/browse/CAMEL-5550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445783#comment-13445783
]
Babak Vahdat commented on CAMEL-5550:
-------------------------------------
Willem
The patch provided by Alan doesn't include any modification for
XQueryBuilder.java, however your commit has changed this source as well causing
the previous commit being reverted!
http://svn.apache.org/viewvc/camel/trunk/components/camel-saxon/src/main/java/org/apache/camel/component/xquery/XQueryBuilder.java?r1=1378534&r2=1379352&pathrev=1379352
> Add headerName option to xpath/xpath language
> ---------------------------------------------
>
> Key: CAMEL-5550
> URL: https://issues.apache.org/jira/browse/CAMEL-5550
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Willem Jiang
> Priority: Minor
> Fix For: 2.11.0
>
> Attachments: CAMEL-5550.patch
>
>
> We recently added headerName to @XPath / @XQuery to support doing xpaths on
> headers. We should add that as well to the xpath/xquery languages so its
> exposed in the DSL, so people can use that.
> For example in a content based router. Today there is some functions that
> return a header, but its a bit cumbersome to use. Maybe people have stored a
> xml in a header, and just want the xpath to evaluate on that.
> The Java / Scala DSL is a bit heavier to add, as it would entail new methods
> in various builder classes to support that. And we got a bunch already for
> the namespaces, and return type etc. So be selective and only add a few for
> the header which makes the most sense. People can always create the
> expression/predicate using the xpath builder itself.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
