1:41 a.m.
The relevant questions are:
1) Why is this element marked as "skip"?
2) Why is this failing only now?
3) Why is this using schema rather than annotations?
On 04/08/2010 05:09 PM, Alexey Loubyansky wrote:
I guess it's the one which is configured to be skipped? Which
test is
failing?
<xs:element name="value">
<xs:annotation>
<xs:appinfo>
<jbxb:skip/>
</xs:appinfo>
</xs:annotation>
<xs:complexType>
<xs:annotation>
<xs:appinfo>
<jbxb:characters>
<jbxb:property name="text"/>
</jbxb:characters>
</xs:appinfo>
</xs:annotation>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="type"
type="xs:string" use="optional">
</xs:attribute>
<xs:attribute name="editor"
type="xs:string" use="optional">
</xs:attribute>
<xs:attribute name="trim"
type="xs:boolean" default="true">
</xs:attribute>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
On 4/8/2010 10:14 PM, John Bailey wrote:
> I have been looking into some testsuite regressions related to the
> JNDIBindingManager not correctly binding values, and I have traced the
> issue back to recent updates (~last month) to the jbossxb JAR. When
> running with one of the 2.0.2.BetaX versions (I tested X= 3|4|5|6), it
> fails to correctly set the value on the JNDIBinding object. When running
> in trace I can see the following messages that may point to an issue:
>
> 2010-04-08 15:06:15,581 TRACE
> [org.jboss.xb.binding.sunday.unmarshalling.XsdBinder] (RMI TCP
> Connection(2)-192.168.1.102) Element
> {urn:jboss:jndi-binding-service:1.0}value added to choice:
> {urn:jboss:jndi-binding-service:1.0}value
> 2010-04-08 15:06:15,581 TRACE
> [org.jboss.xb.binding.sunday.unmarshalling.XsdBinder] (RMI TCP
> Connection(2)-192.168.1.102) element:
> name={urn:jboss:jndi-binding-service:1.0}value, type=null,
> repeatable=false, nillable=false, minOccurs=1, maxOccurs=1, owner type=null
> 2010-04-08 15:06:15,582 TRACE
> [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
> Connection(2)-192.168.1.102)
> http://apache.org/xml/features/validation/dynamic set to: true
> 2010-04-08 15:06:15,582 TRACE
> [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
> Connection(2)-192.168.1.102) Created parser:
> org.apache.xerces.jaxp.SAXParserImpl@51d9b4aa, isNamespaceAware: true,
> isValidating: true, isXIncludeAware: true
> 2010-04-08 15:06:15,583 TRACE
> [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
> Connection(2)-192.168.1.102) Enter startElement
> http://www.w3.org/2001/XMLSchema:annotation
> 2010-04-08 15:06:15,583 TRACE [org.jboss.xb.binding.ObjectModelBuilder]
> (RMI TCP Connection(2)-192.168.1.102) accepted
> http://www.w3.org/2001/XMLSchema:xs:annotation
> 2010-04-08 15:06:15,583 TRACE
> [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
> Connection(2)-192.168.1.102) Exit startElement
> http://www.w3.org/2001/XMLSchema:annotation
> 2010-04-08 15:06:15,583 TRACE
> [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
> Connection(2)-192.168.1.102) Enter startElement
> http://www.w3.org/2001/XMLSchema:appinfo
> 2010-04-08 15:06:15,583 TRACE [org.jboss.xb.binding.ObjectModelBuilder]
> (RMI TCP Connection(2)-192.168.1.102) accepted
> http://www.w3.org/2001/XMLSchema:xs:appinfo
> 2010-04-08 15:06:15,583 TRACE
> [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
> Connection(2)-192.168.1.102) Exit startElement
> http://www.w3.org/2001/XMLSchema:appinfo
> 2010-04-08 15:06:15,583 TRACE
> [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
> Connection(2)-192.168.1.102) Enter startElement
> http://www.jboss.org/xml/ns/jbxb:skip
> 2010-04-08 15:06:15,583 TRACE [org.jboss.xb.binding.ObjectModelBuilder]
> (RMI TCP Connection(2)-192.168.1.102) ignored
> http://www.jboss.org/xml/ns/jbxb:jbxb:skip
> 2010-04-08 15:06:15,583 TRACE
> [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
> Connection(2)-192.168.1.102) Exit startElement
> http://www.jboss.org/xml/ns/jbxb:skip
> 2010-04-08 15:06:15,583 TRACE
> [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
> Connection(2)-192.168.1.102) Enter endElement
> http://www.jboss.org/xml/ns/jbxb:skip
> 2010-04-08 15:06:15,583 TRACE
> [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
> Connection(2)-192.168.1.102) Exit endElement
> http://www.jboss.org/xml/ns/jbxb:skip
> 2010-04-08 15:06:15,583 TRACE
> [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
> Connection(2)-192.168.1.102) Enter endElement
> http://www.w3.org/2001/XMLSchema:appinfo
> 2010-04-08 15:06:15,584 TRACE
> [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
> Connection(2)-192.168.1.102) Exit endElement
> http://www.w3.org/2001/XMLSchema:appinfo
> 2010-04-08 15:06:15,584 TRACE
> [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
> Connection(2)-192.168.1.102) Enter endElement
> http://www.w3.org/2001/XMLSchema:annotation
> 2010-04-08 15:06:15,584 TRACE
> [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (RMI TCP
> Connection(2)-192.168.1.102) Exit endElement
> http://www.w3.org/2001/XMLSchema:annotation
> *2010-04-08 15:06:15,584 TRACE
> [org.jboss.xb.binding.sunday.unmarshalling.XsdBinder] (RMI TCP
> Connection(2)-192.168.1.102) element
> name={urn:jboss:jndi-binding-service:1.0}value: will be skipped, it's
> attributes, character content and children will be set on the parent*
>
>
> I haven't had a chance to dig into what is happening, but I have
> confirmed that falling the jbossxb version back to 2.0.1.GA eliminates
> the issues.
>
> Any ideas?
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
- DML ☍