camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-11074) Unable to load Schematron XSLT templates on windows
Date Mon, 27 Mar 2017 16:05:42 GMT

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

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

Github user jamesnetherton closed the pull request at:

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


> 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
>             Fix For: 2.17.7, 2.18.4, 2.19.0
>
>
> 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)

Mime
View raw message