You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2012/05/31 05:18:27 UTC

[jira] [Comment Edited] (CAMEL-5321) Validator Component Fails on XSD with Classpath Relative Imports

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

Willem Jiang edited comment on CAMEL-5321 at 5/31/12 3:17 AM:
--------------------------------------------------------------

Applied patch into trunk and 2.9.x branch with thanks to Scott.
BTW, I took the test resources which are not included in the patch from the test resource jars.
 
                
      was (Author: njiang):
    Applied patch into trunk and 2.9.x branch.
                  
> Validator Component Fails on XSD with Classpath Relative Imports
> ----------------------------------------------------------------
>
>                 Key: CAMEL-5321
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5321
>             Project: Camel
>          Issue Type: Bug
>    Affects Versions: 2.10.0
>            Reporter: Scott England-Sullivan
>            Assignee: Willem Jiang
>             Fix For: 2.9.3, 2.10.0
>
>         Attachments: CAMEL-5321.patch, camel-validator-test.tar.gz
>
>
> When using the Validator Component with an XSD file from a Jar that contains a relative import, the component will throw a FileNotFoundException.
> This is due to the ObjectHelper.loadResourceAsStream(String) operation attempting to load the classpath resource using file path semantics that will not resolve canonically.
> Test case and patch to follow.
> [Thread Reference|http://camel.465427.n5.nabble.com/org-apache-camel-RuntimeCamelException-java-io-FileNotFoundException-Cannot-find-resource-in-classpaI-td5713557.html]
> Best Regards,
> Scott England-Sullivan
> http://fusesource.com

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira