RE: CDATA Example

In regards to CDATA handling, in XMLBeans < 2.3 there is no way to influence the algorithm that XMLBeans uses to decide when to put a CDATA in the output document and when not to (please note, that from the XML Infoset point of view, use of CDATA section is not relevant as far as the content of the

RE: Schema compilation into XMLBeans classes - issue with several xs:anyType children

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 wildcards, you need to use the XmlCursor API (see the co

RE: Cases in the Namespace?

Hi Andreas, This is an XMLBeans bug (or maybe system limitation of using Java on Windows). You can work around it my remapping one of the URLs to a different package name. For example: http://www.url.com/aBC/myloc";> com.url.abc.myloc in your .xsdconfig file. Radu > -Original Message

RE: XMLBeans 1.0.4 Question about XmlDateTime & xSet* methods

Jacob, Thanks for replying, I'm creating the document from scratch using the code generated from the schema. I'm wondering if it's my use of XmlDateTime that is actually wrong! I created a simple schema which I've included below for reference, with a single xsd:dateTime. Then generated the jar