>> oleClientSite = new OleClientSite(oleFrame, SWT.NONE, >>"opendocument.WriterDocument.1"); > > > That pretty much looks like OLE stuff.
Yes, internalay this oleClient.save method results in a JNI which in turn calls a OleSave function (where ever that comes from).
whereas boolean oleYesOrNo specifies if you would like to include ole information.
I assume you yes "no", so you directly get the file stream and not the OLE storage.
I pass a true value (to leave this yes-no thing), otherwise nothing will be written at all.
The appearance of the filter dialog (as mentioned in your first mail) seems to tell us that the file misses a proper MediaType. Is there a manifest.xml with the correct type added?
No this is missing too.
To my knowledge the file stream OO stores into the OLE storage is a complete OOo document, so it's a miracle to me how something can get lost. Maybe SWT manipulates the file?!
Unlikly as SWT does not know any internals of the embedded document and why should it just pick out the manifest.xml?
Sorry, but I don't know the SWT stuff and how it communicates with OOo. I'm afraid without further information about the internal processes in SWT I can't be of help.
Thank you anyway!
Tobias
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
