Cleanup xsd names for server config
-----------------------------------
Key: AS7-1292
URL:
https://issues.jboss.org/browse/AS7-1292
Project: Application Server 7
Issue Type: Bug
Components: Server
Affects Versions: 7.0.0.Final
Reporter: Wolfgang Knauf
Assignee: Jason Greene
Priority: Minor
Fix For: 7.0.1.Final
From a conversation on the dev mailing list beetween me and Brian:
>> [Wolfgang] If my understanding is correct, the naming of the
server config xsd
>> files is confusing, because a "jboss-7_0.xsd" will be something
>> different than "jboss_6_0.xsd".
>>
>
> [Brian] Yep. Kind of a big DOH!! moment. Looking at the jboss-metadata project
> where these deployment descriptor dtds/xsds come from, I see no
> jboss_6_0.xsd, just jboss_6_0.dtd. And no 7_0 xsd or dtd. But still,
> it's a naming conflict that's bound to bite us unless fixed.
>
> I recommend these server config xds all be renamed to
> jboss-as-XXX_1_0.xsd. They all have an xmlns of
> urn:jboss:domain:XXX:1.0, not 7.0, which IMO is fine since they may get
> revved independently of community AS releases.
>
[Wolfgang} Is there something more I should do - e.g. filing a JIRA issue? Or will
it be fixed by "miracle" ;-) or has someone this already on his todo list ?
[Brian] If you could file a JIRA and assign it to me, Fix Version 7.0.1.Final, I'd
appreciate it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira