Ok, this method works fine for me...
Thanks
Valérie
- Reply to All the Original Message -
Author: Wing Yew Poon
To: user@xmlbeans.apache.org
Date: 10/10/2007 21:23:49
Subject: RE: Réf. : RE: Problem with boolean type
Please see what Cezar wrote on this thread.
I guess to do what you
Yes I get mustUnderstand=true instead of mustUnderstand=1
Valerie
Wing Yew Poon [EMAIL PROTECTED]
09/10/2007 21:40
Veuillez répondre à user
Pour : user@xmlbeans.apache.org
cc :
Objet : RE: Problem with boolean type
Valerie,
what exactly is the incorrect behavior
I recently had a similar problem. A schema defines an element thusly:
xsd:element name=DayWorking type=xsd:boolean minOccurs=0/
When calling the generated interface:
d.setDayWorking(true);
XMLBeans then writes:
DayWorkingtrue/DayWorking
However, the application reading the XML instance
= xo.selectChildren(, a)[0];
axo.set(xb);
System.out.println( xo: + xo);
Cezar
From: Wing Yew Poon [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 10, 2007 1:27 PM
To: user@xmlbeans.apache.org
Subject: RE: Réf. : RE: Problem with boolean type
To: user@xmlbeans.apache.org
Subject: Re: Réf. : RE: Problem with boolean type
I recently had a similar problem. A schema defines an element thusly:
xsd:element name=DayWorking type=xsd:boolean minOccurs=0/
When calling the generated interface:
d.setDayWorking( true );
XMLBeans then writes
= XmlBoolean.Factory.newInstance();
xb.setStringValue(1);
d.xsetDayWorking(xb);
From: Albert Bupp [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 10, 2007 12:08 PM
To: user@xmlbeans.apache.org
Subject: RE: Réf. : RE: Problem with boolean type
I agree that it's not a bug
valid values for the schema type. When XMLBeans
writes the xml, it uses the canonical lexical representation, which is true.
--
From: Albert Bupp [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 10, 2007 8:46 AM
To: user@xmlbeans.apache.org
Subject: Re: Réf. : RE: Problem with boolean type
.
--
*From:* Albert Bupp [mailto:[EMAIL PROTECTED]
*Sent:* Wednesday, October 10, 2007 8:46 AM
*To:* user@xmlbeans.apache.org
*Subject:* Re: Réf. : RE: Problem with boolean type
I recently had a similar problem. A schema defines an element thusly:
xsd:element name
, October 10, 2007 12:08 PM
To: user@xmlbeans.apache.org
Subject: RE: Réf. : RE: Problem with boolean type
I agree that it's not a bug, however, it would
be helpful if there were a way to direct the
setter as to the form to output the value in, as
either true or 1, since both are legitimate
9 matches
Mail list logo