I see that XML Beans 2.3 provides some control over when the saver generates CDATA. The XML Options setSaveCDataLengthThreshold and setSaveCDataEntityCountThreshold allow any of the following configurations:
Every text is CDATA Only text that has an entity is CDATA Only text longer than x chars is CDATA Only text that has y entitazable chars is CDATA Only text longer than x chars and has y entitazable chars is CDATA My question is what is the behavior of the saver in XML Beans 2.2? When does it decide to use CDATA blocks? Thanks, Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]