*To:* user@xmlbeans.apache.org
*Subject:* RE: Schema compilation into XMLBeans classes - issue with
several xs:anyType children
No, this is exactly what I had in mind :-)
Radu
--
*From:* Pascal Maugeri [mailto:[EMAIL PROTECTED]
*Sent:* Monday, May 19, 2008 3:28 AM
Preotiuc-Pietro [mailto:[EMAIL PROTECTED]
Sent: Monday, May 19, 2008 2:12 PM
To: user@xmlbeans.apache.org
Subject: RE: Schema compilation into XMLBeans classes - issue with
several xs:anyType children
No, this is exactly what I had in mind :-)
Radu
From
Thank you Radu for the hint !
What I did to copy a new action element (a RaduAction :-) within actions/
is the following using XmlCursor:
// The action to be inserted within actions/
RaduActionDocument raduActionDoc =
RaduActionDocument.Factory.newInstance();
No, this is exactly what I had in mind :-)
Radu
From: Pascal Maugeri [mailto:[EMAIL PROTECTED]
Sent: Monday, May 19, 2008 3:28 AM
To: user@xmlbeans.apache.org
Subject: Re: Schema compilation into XMLBeans classes - issue
The XmlObject.set() method is common to all generated classes,
regardless of Schema. It just replaces the current value of the
XmlObject with a different value, without changing the reference.
In order to add content in an element allowing any wildcards, you need
to use the XmlCursor API (see
5 matches
Mail list logo