]
ebuzer taha kanat commented on JBMETA-393:
------------------------------------------
Referenced file contains errors (
Missing jboss-web_10_0.xsd on
jboss.org
---------------------------------------
Key: JBMETA-393
URL:
https://issues.jboss.org/browse/JBMETA-393
Project: JBoss Metadata
Issue Type: Bug
Components: web
Reporter: Ladislav Thon
Assignee: Jean-Frederic Clere
Priority: Critical
The {{jboss-web_10_0.xsd}} file we ship with WildFly 10 says at the beginning:
{code:xml}
<jboss-web
xmlns="http://www.jboss.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee
http://www.jboss.org/j2ee/schema/jboss-web_10_0.xsd"
version="10.0">
...
</jboss-web>
Instance documents may indicate the published version of
the schema using the xsi:schemaLocation attribute for the
Java EE namespace with the following location:
http://www.jboss.org/j2ee/schema/jboss-web_10_0.xsd
{code}
So we're pointing people to
http://www.jboss.org/j2ee/schema/, which is a seemingly
arbitrary collection of fairly old files that definitely doesn't contain
{{jboss-web_10_0.xsd}}.
This seems to also be the case for XSDs in previously shipped products, e.g. all
{{jboss-web_7_*.xsd}} files in EAP 6.4 point to the same location.
I found that
http://www.jboss.org/schema/jbossas/ contains a more modern set of XSDs,
but:
- we don't point to it, at least not from {{jboss-web_*.xsd}} files
- it doesn't contain {{jboss-web_10_0.xsd}}
I think the second point should be fairly easy to fix. Hope this is not the wrong place
to report this :-)