[CAMEL-12081] XQuery NPE going from saxon 9.5 to 9.7 (upgraded camel from2.17.4-> 2.20.1)

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Implemented
• Affects Version/s: 2.20.1
• Fix Version/s: 2.21.0
• Component/s: camel-saxon

Environment

JDK 1.8.0_144. Windows 10 and Centos 7

• Estimated Complexity: Unknown
• Assignee: Dmitry Volodin
• Reporter: Riaan Annandale
• Created: 14/Dec/17 06:06
• Updated: 31/Jan/18 06:43
• Resolved: 15/Dec/17 09:12

Description

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

Issue Links

• links to: GitHub Pull Request #2148
• links to: GitHub Pull Request #2148
• links to: GitHub Pull Request #2202