On Fri, 1 Feb 2013, Jon Gorrono wrote:
One possible solution would be to create in intermediate class that is
an immediate ancestor for all the current implementations of the
XMLObject interface ... and which is extended by those classes...
Then, use that class as a place to determine if
the user wants to use custom XMLOptions... for example:
public class CTBubbleScaleImpl extends
org.apache.xmlbeans.impl.values.XmlComplexContentImpl implements
org.openxmlformats.schemas.drawingml.x2006.chart.CTBubbleScale
... create something like
org.poi.something.somethingelse.XmlContextContentImpl extends
org.apache.xmlbeans.impl.values.XmlComplexContentImpl
All of the CT classes are automatically generated by XMLBeans, so I'm not
sure we can easily change the class they extend from. It might be worth
you going back to the xmlbeans list, and seeing how they recommend
allowing for custom XmlOptions on a set of auto-generated schema classes
as large as we have
Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
