Niklas Nebel wrote: > Mathias Bauer wrote: >> For loading and saving document based DocumentInfo objects the XML >> filter currently hands over the document model to the importer/exporter. >> They ask the model for its DocumentInfo and import or export everything >> using the DocumentInfo API. > > From my understanding, that's also how it's supposed to be.
I don't know what "that" is, but I assume that you are talking about using the API. My suggestion is of course to keep import/export via API. What else? I just wanted to encapsulate the code that opens the meta.xml stream and then does Import/Export into single methods of a service DocumentInfo instead of having it as part of the filter. This service is BTW completely independent from any other office code and can be instantiated even outside of OOo. Of course the old code for importing/exporting will still work, as the getDocumentInfo() method of the model will still be present. The new methods are my justification that we only need one service. An object (not only DocumentInfo) always can be either loaded by a dedicated API call or filled by setting every single attribute explicitly (as now). I just felt the need to show that having only one service including persistence handling is applicable to all cases of DocumentInfo - not only standalone. Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[EMAIL PROTECTED]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
