[
https://issues.redhat.com/browse/JBMETA-421?page=com.atlassian.jira.plugi...
]
Brian Stansberry resolved JBMETA-421.
-------------------------------------
Resolution: Won't Do
I'm resolving this as a Won't Do for now. If others see this and feel it's a
good thing to do, please feel free to re-open.
The uses of these Namespace enum values are in parsers for jboss-specific deployment
descriptors that incorporate elements from the EE spec namespaces. Supporting parsing
documents that use the jboss-specific xsds but pull in the Jakarta namespace instead the
JCP one that the jboss xsd specifies is an enhancement for (possible) convenience, not a
requirement.
I'm putting Won't Do on this mostly because I'm not willing to invest the time
to think through whether changes are the right thing to do. I won't do it myself and
don't want to leave this open encouraging others to take on something that seems
trivial but perhaps isn't.
org.jboss.metadata.ejb.parser.jboss.ejb3.Namespace needs to account
for Jakarta
-------------------------------------------------------------------------------
Key: JBMETA-421
URL:
https://issues.redhat.com/browse/JBMETA-421
Project: JBoss Metadata
Issue Type: Enhancement
Components: ejb
Reporter: Brian Stansberry
Priority: Major
Labels: EE9
https://github.com/jboss/metadata/blob/master/ejb/src/main/java/org/jboss...
looks like it needs an entry for
https://jakarta.ee/xml/ns/jakartaee
And then all code that uses that enum should be adapted.
Edit: also org.jboss.metadata.ear.parser.jboss.Namespace.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)