[hibernate-issues] [Hibernate-JIRA] Issue Comment Edited: (HHH-6668) JaxbProcessor can't resolve hibernate-configuration-4.0.xsd

[Emmanuel Bernard (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-6668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43655#comment-43655 ] 

Emmanuel Bernard edited comment on HHH-6668 at 9/20/11 12:11 PM:
-----------------------------------------------------------------

This is fixed and probably must be in 4.0 Final as that will impact many users

      was (Author: emmanuel):
    This is fixed and probably should be in 4.0 Final
  
> JaxbProcessor can't resolve hibernate-configuration-4.0.xsd
> -----------------------------------------------------------
>
>                 Key: HHH-6668
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6668
>             Project: Hibernate Core
>          Issue Type: Bug
>    Affects Versions: 4.0.0.CR3
>            Reporter: Christian Bauer
>            Assignee: Emmanuel Bernard
>            Priority: Trivial
>             Fix For: 4.0.0.next
>
>
> This code in JaxbProcessor.java
> schema = resolveLocalSchema( "/org/hibernate/hibernate-configuration-4.0.xsd" );
> should not use a leading slash, the result will always be null. I'm not sure if the schema-ified version of the config file should be used at all though, doesn't seem to be tested or documented.
> Or the ClassLoaderServiceImpl#locateResource(name) et al. methods should remove leading slashes of names.
> http://download.oracle.com/javase/1.5.0/docs/guide/lang/resources.html
> 'The methods in ClassLoader use the given String as the name of the resource without applying any absolute/relative transformation (see the methods in Class). The name should not have a leading "/".'

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira