[
https://issues.apache.org/jira/browse/CAMEL-12081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16345885#comment-16345885
]
ASF GitHub Bot commented on CAMEL-12081:
----------------------------------------
GitHub user catoaune opened a pull request:
https://github.com/apache/camel/pull/2202
Update xquery-component.adoc
It took me quite a while to figure out that custom functions in Camel 2.18,
2.19 and 2.20 could result in a NullPointerException, so I think it could save
others some time and frustration if there is a note like the one i propose in
the documentation. I can not for sure promise that this will work in 2.21, but
based on the discussions in PR CAMEL-12081, it looks like it will be fixed
there.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/catoaune/camel patch-1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/2202.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2202
----
commit a6157a541ca209799bfabdd7bf8e82e7b46fe161
Author: Cato Aune <cato.aune@...>
Date: 2018-01-30T22:00:42Z
Update xquery-component.adoc
It took me quite a while to figure out that custom functions in Camel 2.18,
2.19 and 2.20 could result in a NullPointerException, so I think it could save
others some time and frustration if there is a note like the one i propose in
the documentation. I can not for sure promise that this will work in 2.21, but
based on the discussions in PR CAMEL-12081, it looks like it will be fixed
there.
----
> XQuery NPE going from saxon 9.5 to 9.7 (upgraded camel from2.17.4-> 2.20.1)
> ---------------------------------------------------------------------------
>
> Key: CAMEL-12081
> URL: https://issues.apache.org/jira/browse/CAMEL-12081
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon
> Affects Versions: 2.20.1
> Environment: JDK 1.8.0_144. Windows 10 and Centos 7
> Reporter: Riaan Annandale
> Assignee: Dmitry Volodin
> Priority: Major
> Fix For: 2.21.0
>
>
> Hi guys
> I think saxon went to 9.7 in camel 2.18 (could be 19). Anyway, I used the
> latest to illustrate my problem (2.20.1 at the time of writing)
> I have a routes that receive XML payloads which I then transform via
> xqueries. Inside these I use local functions for readability (read: it's the
> first thing I tried when solving my problem and it worked).
> Since saxon went to 9.7 I get a null pointer exception when an xquery
> containing a local function tries to process the XML.
> To demonstrate this, I have made a GitHub project:
> [https://github.com/rannandale/xqueryIssue]
> In the project I use two xqueries to transform the same source.
> - One uses an inline for loop:
> <o>
> <variables>{for $v in /root/Data return $v/Name}</variables>
> </o>
> - One uses the local function style:
> declare function local:loopMe($nodes)
> {
> for $node in $nodes
> return
> <variables>{$node/*:Name}</variables>
> };
> <o>
> {local:loopMe(/root/Data)}
> </o>
> The latter is the one that returns the NPE.
> I know I could probably go refactor all my xqueries to match the inline
> style, but I figured I'd see if there is an issue here other than PEBKAC.
> They also get quite complex, so it's quite a bit of work.
> Thanks guys
> Riaan
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
