camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Gosling (JIRA)" <>
Subject [jira] [Commented] (CAMEL-11286) Imported Xquery modules will not resolve using classpath - Regression
Date Thu, 25 May 2017 14:50:04 GMT


Jeremy Gosling commented on CAMEL-11286:

I have a unit test and a one line fix which works on the 2.15.x, 2.16.x and 2.17.x branches,
but fails on 2.18.x and master with a null point exception deep within Saxon.  This appears
to be related to the updated version of the Saxon HE library used.  The fix for the original
enhancement ([CAMEL-4285]) works with any version 9.5.x (9.5.1-5 is specified for Camel 2.15,
2.16 and 2.17) but not 9.6.0-1 onwards.  From Camel 2.18.x onwards various iterations of 9.7
are used, which I'm assuming requires some change to the implementation of the net.sf.saxon.lib.ModuleURIResolver
interface. I'm currently looking into this.

> Imported Xquery modules will not resolve using classpath - Regression
> ---------------------------------------------------------------------
>                 Key: CAMEL-11286
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-saxon
>    Affects Versions: 2.15.0, 2.19.0
>            Reporter: Jeremy Gosling
>            Priority: Minor
>             Fix For: 2.20.0
> In Camel 2.15.0 the camel-saxon component was refactored to include an XQueryEndpoint
class which now instanciates the XQueryBuilder object in the doStart() method.  It then sets
the values of various properties on this object, but misses out the moduleURIResolver.  This
is therefore null when the query is evaluated and not used by the net.sf.saxon.query.XQueryExpression
to resolve xquery module imports as original described in CAMEL-4285. 

This message was sent by Atlassian JIRA

View raw message