[
https://issues.apache.org/jira/browse/CAMEL-12081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16291046#comment-16291046
]
ASF GitHub Bot commented on CAMEL-12081:
----------------------------------------
GitHub user dmvolod opened a pull request:
https://github.com/apache/camel/pull/2148
CAMEL-12081: Cherry-pick commits which are updating saxon from 9.7 to 9.8
This issue is related to saxon and not related to camel-saxon component
implementation.
I've checked provided test on top of the Camel 2.21.0-SNAPSHOT version and
it's working correctly.
This PR is created to update saxon to the version 9.8.0-6 on top of the
Camel 2.20.2.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dmvolod/camel CAMEL-12081
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/2148.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 #2148
----
commit 76154f3d3b05e469d8ca3da562e2659b760adc56
Author: Andrea Cosentino <[email protected]>
Date: 2017-11-23T11:49:07Z
Upgrade Saxon and related bundle to version 9.8.0-5 and regen
commit 5bb67b5c9d3d3c176f5e438bd9e033e2af54435a
Author: Andrea Cosentino <[email protected]>
Date: 2017-12-05T07:31:10Z
Upgrade Saxon and related bundle to version 9.8.0-6
----
> 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
> Fix For: 2.20.2
>
>
> 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
(v6.4.14#64029)
