camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Gosling (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-11286) Imported Xquery modules will not resolve using classpath - Regression
Date Wed, 17 May 2017 11:06:04 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-11286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16013859#comment-16013859
] 

Jeremy Gosling commented on CAMEL-11286:
----------------------------------------

Looks like it was introduced in 2.15.0, and has been in all subsequent versions, including
master.  I'm a currently putting together a minimal unit test which will exhibit the currently
observed behaviour before testing the fix which I will provide.

> Imported Xquery modules will not resolve using classpath - Regression
> ---------------------------------------------------------------------
>
>                 Key: CAMEL-11286
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11286
>             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
(v6.3.15#6346)

Mime
View raw message