camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-4285) Imported Xquery modules will not resolve using classpath
Date Sun, 31 Jul 2011 11:57:09 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-4285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen resolved CAMEL-4285.
--------------------------------

    Resolution: Fixed

Thanks for the patch.

> 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.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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message