hi,

today is our big "find bugs in jibx" day ;-)

we found another one, which partially is already known (as found on  
the mailing list) but i want to add more details.

we use a very "weak" mapping of elements to a class, in the mapping we  
have ordered="false", flexible="true" which allows us to define via an  
XSD how the xml in a specific case has to look like.

as a result, most of the <value> elements within a mapping are with  
usage="optional", and this leads to the following error message:

java.lang.IndexOutOfBoundsException: only START_TAG can have  
attributes TEXT seen ...</id>\r\n\t\t<street>Daham 1<... @10:19
        at org.xmlpull.mxp1.MXParser.getAttributeValue(MXParser.java:927)
        at org.jibx.runtime.impl.XMLPullReaderFactory 
$XMLPullReader.getAttributeValue(XMLPullReaderFactory.java:395)
        at  
org 
.jibx 
.runtime 
.impl.UnmarshallingContext.getAttributeValue(UnmarshallingContext.java: 
356)
        at  
org 
.jibx 
.runtime 
.impl.UnmarshallingContext.attributeBoolean(UnmarshallingContext.java: 
1881)
        at  
data 
.Address 
.JiBX_C__JavaDev322_JiXB_Test_src_customer_binding_unmarshal_1_2 
(Address.java)
        at  
data 
.JiBX_MungeAdapter 
.JiBX_C__JavaDev322_JiXB_Test_src_customer_binding_unmarshal_1_0()
        at  
data 
.Customer 
.JiBX_C__JavaDev322_JiXB_Test_src_customer_binding_unmarshal_1_0 
(Customer.java)
        at  
data 
.JiBX_C__JavaDev322_JiXB_Test_src_customer_bindingCustomer_access2 
.unmarshal()
        at  
org 
.jibx 
.runtime 
.impl.UnmarshallingContext.unmarshalElement(UnmarshallingContext.java: 
2537)
        at  
org 
.jibx 
.runtime 
.impl.UnmarshallingContext.unmarshalDocument(UnmarshallingContext.java: 
2680)
        at test.CustomerWAddressTest.main(CustomerWAddressTest.java:23)

when only the first <value> is with usage="optional", and the rest is  
with usage="required", everything works fine, but of course this  
doesn't map to the real XML content where all of the value-entries are  
optional!

we have no idea how to build a workaround for that, so it would be  
cool to know if the fix for this will go into the next release 1.1.6  
and when this release will be available, because we're stuck in  
production now...

if anyone has an idea for a workaround please let me know! thanks in  
advance!

br,
günther

-- 
Günther Wieser
creative-it
Guglgasse 6/1/11/1
A-1110 Wien
[EMAIL PROTECTED]
http://www.creative-it.com




-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
jibx-users mailing list
jibx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-users

Reply via email to