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.

Emmanuel says he is going to open one. In fact, he says he already raised the same issue in the forums but then forgot about it. :-) On Tue, 2008-10-28 at 12:19 +0100, Carlo de Wolf wrote: > Could you open a jira for this one and mark it as critical? > Preferably I like the test cases committed under that issue as well, but > that is water under the bridge. Or is that mustard after the cake. > > Carlo > > 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. >> >> > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development >

Could you open a jira for this one and mark it as critical? Preferably I like the test cases committed under that issue as well, but that is water under the bridge. Or is that mustard after the cake.

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.