Raymond, > 1) What's the use case to save a XMLDocument or DataObject to the > XMLStreamWriter? If there's no such requirement, we can get rid of them.
Well, part of the work we are doing in Celtix is to allow the "databinding" layer to write directly toward a XMLStreamWriter. I was hoping to use those methods since that is ideal. > 2) With the createStreamReader() method, we can easily pipe the reader to > writer with a utility (Axiom has one). Here's the implementation in my > latest patch. > > XMLStreamReader reader = createXMLStreamReader(document); > new XMLStreamSerializer().serialize(reader, writer); // > XMLStreamSerializer is the utility to pull events from the reader and dump > them into the writer What is the performance impact of doing that? I'm OK with doing something like that (and maybe even making the mentioned save() and saveObject() methods do that) if there isn't a major performance issue with doing that. Basically, the goal is to get the objects written out to a stream as quickly as possible. If "reading events from one stream and pumping them to the output stream" isn't too bad, I'm OK with it. But if there is a performance impact of doing that, then I would suggest leaving the ability to write directly to the XMLStreamWriter. Thanks! -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 F:781-902-8001 [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
