Hi Ozgur,
In that case Castor behavior is the *expected* one:
<xs:element name="p">
<xs:complexType mixed="true">
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:element name="b" type="xs:string"
minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
the element 'P' can have multiple items (that can from the sequence) and
one character content (that comes from the mixed='true').
When unmarshalling a xml with some text content, Castor can't save by
now the place where this content occurred.
Putting the 'content' field in Item is not the required behavior: an
item class represents what can occur in the sequence (what kind of
element or attribute).
The main reason for not saving the order of appearance of a character
content lies in the data-binding character of Castor XML: Castor just
needs to save the information, it is not a serializer by itself.
Maybe future versions will allow that but it is not on our to-do list
right now.
You can still use <any> or XSLT...
Sorry for the late reply,
Arnaud
> -----Original Message-----
> From: Ozgur Balsoy [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 21, 2002 3:49 AM
> To: [EMAIL PROTECTED]
> Subject: [castor-dev] mixed-case bug status? [Re: wrongly placed
> attributes]
>
> Arnaud,
>
> Were you able to look at the bug I had posted in this message (
> http://www.mail-archive.com/[email protected]/msg04177.html )?
>
> Is it in bugzilla?
>
> Ozgur
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
