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:
<DayWorking>true</DayWorking>
However, the application reading the XML instance
(which is out of my control) needs it to be:
<DayWorking>1</DayWorking>
My work-around was to revise the schema to
declare the element type as an integer, regenerate the library.
It would be nice, though if there was a way of
optionally directing to the boolean type setter
method to write the value as a numeric value.
Cheers, Albert
At 05:16 AM 10/10/2007, you wrote:
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 you are seeing?
Are you saying that the xml that is marshalled
is incorrect after calling the setter? i.e., you
call setMustUnderstand(true) and the xml shows
mustUnderstand="true" instead of mustUnderstand="1"?
- Wing Yew
----------
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 09, 2007 6:53 AM
To: user@xmlbeans.apache.org
Subject: Problem with boolean type
I have the following schema element :
<xs:attribute name="mustUnderstand">
<xs:simpleType>
<xs:restriction base="xs:boolean">
<xs:pattern value="0|1"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
Xbean generates the following accessors :
void setMustUnderstand(boolean mustUnderstand);
boolean getMustUnderstand();
This result in an xml attribute with value
"true" or "false" : it is not correct regarding the schema !
Is there anything to do to correct it?
Notice: This email message, together with any
attachments, may contain information of BEA
Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary,
copyrighted and/or legally privileged, and is
intended solely for the use of the individual or
entity named in this message. If you are not the
intended recipient, and have received this
message in error, please immediately return this by email and then delete it.