[
https://issues.apache.org/jira/browse/CAMEL-10653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15773469#comment-15773469
]
Nikolay Voskresenskiy commented on CAMEL-10653:
-----------------------------------------------
Looks like explicitly specifying the type of the external variable now seems to
make it work:
{code}
declare variable $in.headers.testHeader as xs:string external;
<header>{$in.headers.testHeader}</header>
{code}
I would suggest clarifying how to use the Variables as parameters in the xquery
component documentation
> XQuery support broken in Camel 2.18.x
> -------------------------------------
>
> Key: CAMEL-10653
> URL: https://issues.apache.org/jira/browse/CAMEL-10653
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon
> Affects Versions: 2.18.0, 2.18.1
> Reporter: Nikolay Voskresenskiy
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.18.2, 2.19.0
>
> Attachments: camel-xquery-test.zip
>
>
> The camel xquery support no longer works correctly as of 2.18.x
> I identified two main issues so far:
> # A java.lang.NullPointerException is thrown when exchange contains any null
> headers or properties:
> {code}
> java.lang.NullPointerException: External object cannot wrap a Java null
> at net.sf.saxon.value.ObjectValue.<init>(ObjectValue.java:55)
> at
> org.apache.camel.component.xquery.XQueryBuilder.addParameters(XQueryBuilder.java:640)
> {code}
> # An error in execution whenever a header or a property are referenced in the
> xquery as an external variable:
> {code}
> java.lang.AssertionError: Unknown event
> at
> net.sf.saxon.evpull.ComplexContentProcessor.advance(ComplexContentProcessor.java:198)
> {code}
> Attached is a maven project with junit test illustrating the issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
