[jboss-jira] [JBoss JIRA] Closed: (JBXB-205) element name shouldn't be assigned to schemaLocation if namespace is not null

Alexey Loubyansky (JIRA) jira-events at lists.jboss.org
Thu Jun 4 05:22:56 EDT 2009


     [ https://jira.jboss.org/jira/browse/JBXB-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Loubyansky closed JBXB-205.
----------------------------------

    Resolution: Done


Done.

> element name shouldn't be assigned to schemaLocation if namespace is not null
> -----------------------------------------------------------------------------
>
>                 Key: JBXB-205
>                 URL: https://jira.jboss.org/jira/browse/JBXB-205
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Bug
>    Affects Versions: JBossXB-2.0.1.GA
>            Reporter: Alexey Loubyansky
>            Assignee: Alexey Loubyansky
>             Fix For: JBossXB-2.0.2.GA
>
>
> In SundayContentHandler before schema resolution if schemaLocation was not provided in XML and DTD systemId is not available, schemaLocation is assigned to the localName of the element. This is useful for XML files that are validated against DTDs (or don't use a specific namespace). But if the namespace is not null there comes a problem since non-null schema location will override the one used in JBossEntityResolver (making mapping of nsURI to schemaLocation in the resolver useless).
> So, assigning schemaLocation to localName should be done only for schemas that don't use namespaces.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list