[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: AW: [sdo] Code for SDOSource, SDOResult and ContentHandler
Hi Stefan, The JAXBSource class comes with a big disclaimer: http://java.sun.com/javase/6/docs/api/javax/xml/bind/util/JAXBSource.html "The fact that JAXBSource derives from SAXSource is an implementation detail. Thus in general applications are strongly discouraged from accessing methods defined on SAXSource. In particular, the setXMLReader and setInputSource methods shall never be called. The XMLReader object obtained by the getXMLReader method shall be used only for parsing the InputSource object returned by the getInputSource method. " I believe we should follow this lead with SDOSource. In other words SDOSource is not really a SAXSource, it only extends SAXSource because it's the least objectionable option. Users should not expect calls to SAXSource APIs to work. Instead they should use SDOSource specific API. Here we can control the entry points, the options parameter on the constructor is how the user specifies the desired behaviour. Ultimately you require "http://xml.org/sax/features/namespace-prefixes" support at the XMLHelper level. It doesn't matter what you set on the reader the XMLHelper.save method is what needs to do the work. Of course we can make this standard or leave it proprietary. If you can enable the "http://xml.org/sax/features/namespace-prefixes" feature in SDOSource, then it seems logical at the user would want this ability when using the XMLHelper.save method with a SAXResult, or in the future if we add a save method that takes a ContentHandler. -Blaise Buennig, Stefan wrote: 45E8ACF4DC4D7148AB9A906B6B216DAD01E06BF5@dewdfe1m.wdf.sap.corp" type="cite"> |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]