This content has been marked as final.
Show 7 replies
-
1. Re: jboss-classload*.xsd appears to be broken
dmlloyd Sep 17, 2008 10:38 AM (in response to dmlloyd)Also I found that "capabilities" was misspelled in a few places in the .xsd...
-
2. Re: jboss-classload*.xsd appears to be broken
dmlloyd Sep 17, 2008 10:46 AM (in response to dmlloyd)"david.lloyd@jboss.com" wrote:
Also IDEA seems fairly certain that you can't use the "base" attribute here, though I'm not sharp enough on my xsd to say for sure:<xsd:simpleType name="version" base="xsd:string">
It's all coming back to me. Perhaps this should be:<xsd:simpleType name="version"> <xsd:annotation> <xsd:documentation> <![CDATA[ A version. ]]> </xsd:documentation> </xsd:annotation> <xsd:restriction base="xsd:string"/> </xsd:simpleType>
And export-all should probably be:<xsd:simpleType name="export-all"> <xsd:annotation> <xsd:documentation> <![CDATA[ Whether to export all, valid values are: ALL = export every package NON_EMPTY = only export packages that have contents ]]> </xsd:documentation> </xsd:annotation> <xsd:restriction base="xsd:string"> <xsd:enumeration value="ALL"/> <xsd:enumeration value="NON_EMPTY"/> </xsd:restriction> </xsd:simpleType>
What do you think? I can commit this if it's not a bad time release-wise. -
3. Re: jboss-classload*.xsd appears to be broken
starksm64 Sep 17, 2008 1:01 PM (in response to dmlloyd)These are definitely broken, but have not been updated for months. I would guess its because we are now using jaxb annotations to describe the schema, so these files would need to be synced with the current jaxb usage.
-
4. Re: jboss-classload*.xsd appears to be broken
dmlloyd Sep 17, 2008 1:25 PM (in response to dmlloyd)Oh well. Well I just committed the simple fix - if nothing is using these for validation then at least nothing will break. But we probably ought to employ (or create) a schema verification tool that compares the annotation-based rules to the xsd and warns about any glaring incompatibilities...
-
5. Re: jboss-classload*.xsd appears to be broken
alesj Sep 29, 2008 9:43 AM (in response to dmlloyd)"david.lloyd@jboss.com" wrote:
Oh well. Well I just committed the simple fix - if nothing is using these for validation then at least nothing will break.
You should also port this to Branch_2_0:
- http://anonsvn.jboss.org/repos/jbossas/projects/jboss-cl/branches/Branch_2_0/"david.lloyd@jboss.com" wrote:
But we probably ought to employ (or create) a schema verification tool that compares the annotation-based rules to the xsd and warns about any glaring incompatibilities...
I'll do something about this.
Probably - as discussed in Neuchatel - adding default validation against .xsd file based schema. -
6. Re: jboss-classload*.xsd appears to be broken
alesj Oct 3, 2008 8:03 AM (in response to dmlloyd)"alesj" wrote:
You should also port this to Branch_2_0:
- http://anonsvn.jboss.org/repos/jbossas/projects/jboss-cl/branches/Branch_2_0/
Ported. -
7. Re: jboss-classload*.xsd appears to be broken
dmlloyd Oct 3, 2008 10:30 AM (in response to dmlloyd)Thanks, sorry. Have been a bit distracted by other things.