Thursday, August 8, 2002 07:54 AM
The short answer is no. The long answer involves some additional questions:
- Why do you want to involve JNI in an document conversion?
If you need to convert a Microsoft document to XML, you could easily design a native application that does that and call it through the Java process API.
- Do you really need the in-process, fine-grained access to the document that JNI would allow you?
Unless I'm missing something, you probably want to convert the document to XML only to use it from Java. For that you don't need JNI because once the document is XML, you can access it through Java's XML libraries.
If you truely need to access the Microsoft document from Java, JNI could be used to write wrappers around the COM interfaces of your Microsoft apps.