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

ASF GitHub Bot commented on CAMEL-11074:
----------------------------------------

GitHub user jamesnetherton opened a pull request:

    https://github.com/apache/camel/pull/1578

    CAMEL-11074: Unable to load Schematron XSLT templates on windows

    https://issues.apache.org/jira/browse/CAMEL-11074

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jamesnetherton/camel CAMEL-11074

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/1578.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1578
    
----
commit 6bd6eec5a6d12174d745bd7ddefbf4abb83cab69
Author: James Netherton <[email protected]>
Date:   2017-03-27T15:19:07Z

    CAMEL-11074: Unable to load Schematron XSLT templates on windows

----


> Unable to load Schematron XSLT templates on windows
> ---------------------------------------------------
>
>                 Key: CAMEL-11074
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11074
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-schematron
>    Affects Versions: 2.18.3, 2.19.0
>            Reporter: James Netherton
>            Assignee: James Netherton
>
> Similar to CAMEL-8504. {{ClassPathURIResolver}} does:
> {code}
> InputStream stream = ClassPathURIResolver.class.getClassLoader()      
>     .getResourceAsStream(rulesDir.concat(File.separator).concat(href));
> {code}
> Depending on the ClassLoader implementation, platform dependent paths for 
> resource lookups are not guaranteed to work (which arguably could be 
> considered a bug in the ClassLoader impl).
> Looking at the git history, it seems this code has swapped between using 
> {{File.separator}} and {{"/"}} a few times now. However, I see no clear 
> reason why we need to use {{File.separator}} in the resource lookup. {{"/"}} 
> should work perfectly fine in all cases. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to