Yes, that's it. The fix is in the metadata's trunk.
Dimitris Andreadis wrote:
It's reproducible with both jrockit16 and sun16 jvms. Just switch
to
jdk6, run jboss one one side and testsuite>build one-test
-Dtest=org.jboss.test.web.test.WebIntegrationUnitTestCase on the other.
I think this also explains the differences we get in the jdk5 vs jdk6
runs (~ 4-8 additional failed tests).
Alexey Loubyansky wrote:
> I guess, it's related to the order in which binding annotations are
> processed. So, role-name in the bound schema appears before the
> description.
> In many metadata classes propOrder is still not specified (I've been
> adding it to the types I touched during refactorings) and assumed that
> the properties will be bound in the order they appear in the class
> source and inherited.
>
> Is this reproducible 100% with that JDK version? I'll add the
> propOrder to every type where the role-name appears to see if that's
> the problem.
>
>
> Alexey
>
> Dimitris Andreadis wrote:
>> The org.jboss.test.web.test.WebIntegrationUnitTestCase passes when
>> run under jdk5, but break under jdk6:
>>
>>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>>
>>
>> Something to do with the xml parsing:
>>
>>
vfszip:/qa/hudson_ws/workspace/JBoss-AS-5.0.x-TestSuite-jrockit16-jrockit16/trunk/testsuite/output/lib/jbosstest-web.ear
>> -> org.jboss.xb.binding.JBossXBRuntimeException: Requested element
>> {http://java.sun.com/xml/ns/j2ee}description is not allowed in this
>> position in the sequence. The next element should be
>> {http://java.sun.com/xml/ns/j2ee}role-name
>>
>>