[
https://issues.jboss.org/browse/WFLY-3961?page=com.atlassian.jira.plugin....
]
Jay Kumar SenSharma updated WFLY-3961:
--------------------------------------
Description:
The Feature Request:
https://issues.jboss.org/browse/WFLY-3014
Does not address the actual issue.
- It is understood that we do not validate the xml with it. However there are some users
who reads the XSD via valid schemaLocation and parse them according to their requirement
for XML processing.
- The XSDs that are shipped with wildfly uses a non existing "schemaLocation".
For example: "jboss-web_8_0.xsd"
{code}
<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_8_0.xsd"
version="8.0">
...
</jboss-web>
{code}
- The schema location points to
http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd (causes
404 http response) Where as all those XSDs are actually present in another location,
http://www.jboss.org/schema/jbossas/ So for the "jboss-web_8_0.xsd" the correct
schemaLocation should be
http://www.jboss.org/schema/jbossas/jboss-web_8_0.xsd
So in order to avoid confusion to the users who are more familiar with XML/XSD naming
the "schemaLocation" should be corrected in all the XSDs.
*Expectation:* Either the XSDs should point to a valid existing URL. Or the XSDs should be
corrected to alter the Schema locations from non-existing
http://www.jboss.org/j2ee/schema/ (which has very few XSDs) to
http://www.jboss.org/schema/jbossas/ (which has almost all the updated xsds)
was:
The Feature Request:
https://issues.jboss.org/browse/WFLY-3014
Does not address the actuall issue.
- It is understood that we do not validate the xml with it. However there are some users
who reads the XSD via valid schemaLocation and parse them according to their requirement
for XML processing.
- The XSDs that are shipped with wildfly uses a non existing "schemaLocation".
For example: "jboss-web_8_0.xsd"
{code}
<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_8_0.xsd"
version="8.0">
...
</jboss-web>
{code}
- The schema location points to
"http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd" Where as all those XSDs are
actually present in another location, "http://www.jboss.org/schema/jbossas/" So
for the "jboss-web_8_0.xsd" the correct schemaLocation should be
"http://www.jboss.org/schema/jbossas/jboss-web_8_0.xsd"
So in order to avoid confusion to the users who are more familiar with XML/XSD naming
the "schemaLocation" should be corrected in all the XSDs.
*Expectation:* Either the XSDs should point to a valid existing URL. Or the XSDs should be
corrected to alter the Schema locations from non-existing
"http://www.jboss.org/j2ee/schema/...." (which has very few XSDs) to
""http://www.jboss.org/schema/jbossas/...." (which has almost all the
updated xsds)
XSDs should use a correct and existing schemaLocation.
------------------------------------------------------
Key: WFLY-3961
URL:
https://issues.jboss.org/browse/WFLY-3961
Project: WildFly
Issue Type: Bug
Affects Versions: 8.1.0.Final, 9.0.0.Alpha1
Environment: All
Reporter: Jay Kumar SenSharma
Assignee: Jason Greene
Labels: xml, xml_schema
The Feature Request:
https://issues.jboss.org/browse/WFLY-3014
Does not address the actual issue.
- It is understood that we do not validate the xml with it. However there are some users
who reads the XSD via valid schemaLocation and parse them according to their requirement
for XML processing.
- The XSDs that are shipped with wildfly uses a non existing "schemaLocation".
For example: "jboss-web_8_0.xsd"
{code}
<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_8_0.xsd"
version="8.0">
...
</jboss-web>
{code}
- The schema location points to
http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd
(causes 404 http response) Where as all those XSDs are actually present in another
location,
http://www.jboss.org/schema/jbossas/ So for the "jboss-web_8_0.xsd"
the correct schemaLocation should be
http://www.jboss.org/schema/jbossas/jboss-web_8_0.xsd
So in order to avoid confusion to the users who are more familiar with XML/XSD naming
the "schemaLocation" should be corrected in all the XSDs.
*Expectation:* Either the XSDs should point to a valid existing URL. Or the XSDs should
be corrected to alter the Schema locations from non-existing
http://www.jboss.org/j2ee/schema/ (which has very few XSDs) to
http://www.jboss.org/schema/jbossas/ (which has almost all the updated xsds)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)