[
https://issues.apache.org/jira/browse/CAMEL-12081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16291571#comment-16291571
]
ASF GitHub Bot commented on CAMEL-12081:
----------------------------------------
davsclaus commented on issue #2148: CAMEL-12081: Cherry-pick commits which are
updating saxon from 9.7 to 9.8
URL: https://github.com/apache/camel/pull/2148#issuecomment-351828513
Hmm this is good and bad at the same time. Because doing a non-patch upgrade
on a patch branch is not always so good. What if it breaks other things. That
user whom had a problem can just wait for Camel 2.21 to upgrade, or upgrade
saxon himself.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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)
