[jboss-jira] [JBoss JIRA] Commented: (JBAS-2282) JBossEntityResolver is not using schemaLocation URIs that are valid non-file URLs

[Alexey Loubyansky (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBAS-2282?page=comments#action_12378735 ] 
            
Alexey Loubyansky commented on JBAS-2282:
-----------------------------------------

The patch seems to be a fork of http://xml.apache.org/commons. Was there a reason not to use the original?..

> JBossEntityResolver is not using schemaLocation URIs that are valid non-file URLs
> ---------------------------------------------------------------------------------
>
>                 Key: JBAS-2282
>                 URL: http://jira.jboss.com/jira/browse/JBAS-2282
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: XML services
>    Affects Versions:  JBossAS-4.0.3RC2
>            Reporter: Scott M Stark
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossAS-4.2.2.GA
>
>         Attachments: jboss-entity-resolver.zip
>
>
> The org.jboss.util.xml.JBossEntityResolver is not dealing with systemIDs that are valid non-file URLs. For example, this xml fragment from a testcase which uses the jboss resource URL:
> <?xml version="1.0" encoding="UTF-8"?>
> <!-- $Id: config.xml,v 1.1 2005/07/31 23:13:44 starksm Exp $ -->
> <jaas:policy
>    xsi:schemaLocation="urn:jboss:security-config resource:security-config_4_1.xsd"
>    xmlns:jaas="urn:jboss:security-config"
>    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>    >
> does map to a valid URL which can be loaded, but the parsing of this URL by the getLocalEntityName ends up throwing away the full path info to produce a resource name of schema/security-config_4_1.xsd. This would work inside the jboss server provided the security-config_4_1.xsd is bundled into a classpath location following the location conventions expected by the JBossEntityResolver, but does not work in the testsuite where this is not the case, and would not work for user defined schemas located elsewhere. It would seem we should try to load the schema from systemIDs that are valid URLs before defaulting to the jboss specific logic.

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