[
https://jira.jboss.org/jira/browse/JBMETA-185?page=com.atlassian.jira.plu...
]
Alexey Loubyansky closed JBMETA-185.
------------------------------------
Resolution: Done
- the namespace
http://www.jboss.org/j2ee/schema in the comments and examples in
jboss_5_[0/1].xsd has been changed to
http://www.jboss.com/xml/ns/javaee.
- schema location in the import of the ejb spec schema has been changed from
ejb-jar_3_0.xsd to
http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd (in JBoss, this has
no effect since both locations will be resolved locally but correct remote location may
help other validating tools)
The following issues have been resolved in previous metadata releases:
- redundant security-identity elements have been removed
- version attribute of jboss element has been changed from 'fixed' to
'default' with value 5.0, i.e.
<xsd:attribute name="version" type="javaee:dewey-versionType"
default="5.0">
Use external schemaLocation for ejb-jar_3_0.xsd in jboss_5_X.xsd and
docs corrections
-------------------------------------------------------------------------------------
Key: JBMETA-185
URL:
https://jira.jboss.org/jira/browse/JBMETA-185
Project: JBoss Metadata
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.0.CR17
Reporter: Alexey Loubyansky
Assignee: Alexey Loubyansky
Fix For: 1.0.1.Beta1
This issue addresses issues raised in JBAS-6426 that haven't been resolved yet.
--
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