[
https://issues.apache.org/jira/browse/CAMEL-4285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012433#comment-16012433
]
Jeremy Gosling commented on CAMEL-4285:
---------------------------------------
This appears to have been regressed since 2.15.0. See [CAMEL-11286]
> Imported Xquery modules will not resolve using classpath
> --------------------------------------------------------
>
> Key: CAMEL-4285
> URL: https://issues.apache.org/jira/browse/CAMEL-4285
> Project: Camel
> Issue Type: Improvement
> Components: camel-saxon
> Affects Versions: 2.8.0
> Environment: All
> Reporter: Jay mann
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.8.2, 2.9.0
>
> Attachments: camel-saxon.patch
>
>
> When using an xquery endpoint that uses an xquery file like this:
> <camel:to uri="xquery:com/test/xquery/manual.xq"/>
> If the manual.xq file contains imported modules such as:
> import module namespace utils = "myutils" at "classpath:/com/test/utils.xq";
> they will not resolve relative to the classpath.
> This is a big problem when using OSGI or any other situation where your
> Xquery files are inside your package/jar.
> I've created a patch so that it will resolve the imports in the same way that
> the component resolves resources using resolveMandatoryResource.
> I've tested the patch successfully using "classpath:/", "file://", and
> "http://"; uri formats.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
