You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Willem Jiang (Commented) (JIRA)" <ji...@apache.org> on 2012/02/06 15:21:59 UTC
[jira] [Commented] (CAMEL-4970) Cannot use xquery predicate in
filter after an xpath splitter.
[ https://issues.apache.org/jira/browse/CAMEL-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201307#comment-13201307 ]
Willem Jiang commented on CAMEL-4970:
-------------------------------------
This issue is introduced by the enhancement of the XmlConverter to support the stax API better. When turning the Element to a DOMSource, we should create a Document first and then create a DomSource based on the Document.
> Cannot use xquery predicate in filter after an xpath splitter.
> ----------------------------------------------------------------
>
> Key: CAMEL-4970
> URL: https://issues.apache.org/jira/browse/CAMEL-4970
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon
> Affects Versions: 2.9.0
> Reporter: Lefteris Tsallas
> Assignee: Willem Jiang
> Labels: xpath, xquery
> Attachments: XqueryPredicateFilterTest.java
>
>
> After upgrading from 2.5.0 to 2.9.0 using xqury predicate after an xpath filter throws java.lang.ClassCastException: net.sf.saxon.tinytree.TinyElementImpl cannot be cast to net.sf.saxon.om.DocumentInfo . Attached unit test doesn't fail in camel 2.5.0.
> from("direct:xpath")
> .split(xpathsplitter)
> .filter().xquery("//record[type=2]")
> .to("mock:result");
> See nabble discussion http://camel.465427.n5.nabble.com/Unit-test-fails-after-upgrading-to-2-7-1-Cannot-use-xquery-expression-after-xpath-td4422582.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira