Tobias Himstedt wrote: >>>Unlikly as SWT does not know any internals of the embedded document and >>>why should it just pick out the manifest.xml? >> >> >> I puzzled about this. If OOo documents are embedded as OLE servers they >> store themselves as OLE storage that contains a stream named >> "package_stream" and contains the whole zip file as usual. So an OleSave >> should give you the OLE storage (that does not look like a zip file, so >> it's not what you obviously got). > > So, what do you think. Is there anything I can do about this and is it > more likely an OpenOffice or a SWT problem?
As long as I don't know what SWT exactly does I can only guess. In general I wouldn't see this as an OOo problem, because I know the OLE implementation of OOo works in several OLE clients. Maybe someone who has the source code of SWT *and* understands it can tell us more. > Meanwhile I played around with this UNO stuff and was able to embed a > OpenOffice in a java.awt.Frame. Would you consider this as a usable and > stable alternative? Yes, definitely. This is one of the recommended ways we can offer. And the biggest benefit might be that if something goes wrong we will have a better chance to tell you why. :-) Best regards, Mathias -- Mathias Bauer - OpenOffice.org Application Framework Project Lead Please reply to the list only, [EMAIL PROTECTED] is a spam sink. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
