[jboss-jira] [JBoss JIRA] Commented: (JBMETA-5) jboss-metadata.jar needs refresh of schema/web-app_2_4.xsd

[Darryl Miles (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBMETA-5?page=comments#action_12401882 ] 
            
Darryl Miles commented on JBMETA-5:
-----------------------------------

You are correct it is a Tomcat issue in nature, but the XML parser provided by JBoss AS to Tomcat is a validating parser by default.  This parser has its own XSD locator which I guess looks inside 
jboss-metadata.jar.  The web-app_2_4.xsd inside jboss-metadata.jar is now out of date (with respect to the mime-type regex pattern from the current web-app_2_4.xsd published by  Sun.)


The web-app_2_4.xsd is correct in all recent versions of Tomcat 5.5.x and I've been told that since Tomcat 6.0.16 (I think JBoss AS 5 Beta4 ships with 6.0.14 and I'm sure by the time it goes final it will be updated with >= 6.0.16 so the out-of-date files in servlet-api.jar will get updated).

I manually corrected the web-app_2_4.xsd in servlet.jar from 6.0.14 thats shipped inside JBoss AS 5 Beta4) and the error did not go away.


It was only after I manually corrected the web-app_2_4.xsd in jboss-metadata.jar that the error went away.  My thinking on this is that JBoss provides Tomcat with the XML parser configured the JBoss way, with validation enabled etc...

So this bug report is to get the web-app_2_4.xsd inside jboss-metadata.jar updated.  Maybe you have a script that can download and diff the original published XSD/DTDs to help manage the jboss-metadata.jar so you can see which need a refresh for each release of JBoss.


> jboss-metadata.jar needs refresh of schema/web-app_2_4.xsd
> ----------------------------------------------------------
>
>                 Key: JBMETA-5
>                 URL: http://jira.jboss.com/jira/browse/JBMETA-5
>             Project: JBoss Metadata
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Darryl Miles
>         Assigned To: Alexey Loubyansky
>
> The main concern is that the regex for validating:
> <mime-mapping>
>         <extension>xhtml</extension>
>         <mime-type>application/xhtml+xml</mime-type>
> </mime-mapping>
> The "+" character is not allowed by the older regex but its valid for a MIME type and at this time with the default out-the-box configuration of JBoss 5 any web-app using the above mime-mapping can not be deployed as the parser validates the XSD.
> Is incorrect, Sun fixed their XSD sometime ago now to change:
> --- web-app_2_4.xsd     2008-03-02 00:49:56.000000000
> +0000
> +++ ../web-app_2_4.xsd  2007-12-18 09:05:06.000000000 +0000
> @@ -805,7 +798,7 @@
>      <xsd:simpleContent>
>        <xsd:restriction base="j2ee:string">
> -       <xsd:pattern value="[\p{L}\-\p{Nd}]+/[\p{L}\-\p{Nd}\.]+"/>
> +       <xsd:pattern value="[^\p{Cc}^\s]+/[^\p{Cc}^\s]+"/>
>        </xsd:restriction>
>      </xsd:simpleContent>
>    </xsd:complexType>
> See also Tomcat 6 Bugzilla entry: https://issues.apache.org/bugzilla/show_bug.cgi?id=44517
> Also Sun have released a newer schema/web-app_2_5.xsd maybe that should be updated too, but the regex in the currently shipped one is okay with regards to this regex but I'm sure there have been other changes as bug in the original web-app_2_5.xsd have been worked out for the new 2.5 technology.

-- 
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