Re: [jboss-dev] JBoss_5_0.xsd is wrong
FYI, I started with a simple test (I chose XSModel instead of the
SchemaPrinter). Even though it's still incomplete it already shows that
the xsd and annotations are far from being consistent.
- missing types and elements
- a type in schema and in metadata may have different names
- one class in metadata maybe re-used for different types in xsd (but of
course it can be bound only to one xsd type with @XmlType)
So, it's gonna take some time to bring it all together. Even only for
jboss_5_0.xsd/JBossMetaData ;)
As a quick fix, I would just add the elements that make the
DDValidatorUnitTestCase fail and work on the rest afterwards.
Adrian Brock wrote:
As part of a test of this
https://jira.jboss.org/jira/browse/JBAS-6013
I've created a test that uses the jboss_5_0.xsd
for an MDB.
The test works but the
org.jboss.test.xml.DDValidatorUnitTestCase
is saying my jboss.xml is invalid
The reason is that the xsd says I can't have
an <activation-config/> in jboss.xml
This is obviously wrong since it works
and JBossMessageDrivenMetaData has such an element.
In fact, there are many things you can now have
in jboss.xml (virtually anything from ejb-jar.xml)
that are not listed in this schema.
I'm going to commit this and leave it to somebody
working on the metadata project to fix the schema
and therefore the test.
Using this class
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/common/jbossxb/trunk/src/test/...
with the SchemaBinding created by the schema builder
will help in seeing the difference in the actual
versus the documented schema.
Under the new rules, I should be allowed to
break the testsuite if it shows something is broken.