Mike Traum wrote:
I'm developing an external, command-line java application that interfaces with oo 2.0. I'd prefer to bundle the oo jar's I use (juh.jar, jurt.jar, ridl.jar, unoil.jar) so that I don't have to deal with trying to find the location of the user's openoffice installation to set the classpath.
Is this an acceptable way of doing this, or will the api change so that every time a new OO point release comes out, I'm going to have to repackage my application.
Your approach should work (as long as you use those jars in compliance with their license, which shouldn't be much of a problem for LGPL), as we try to keep UNO backward compatible. (You won't benefit from any improvements, of course.)
On second thought, while this approach should be binary compatible, you could still encounter a kind of build incompatibility, when you re-build your application against a new version of OOo where one of the JARs you include from OOo now depends on an additional JAR from OOo which you do not include. One more reason to go with the "Simple Bootstrap" solution...
-Stephan
However, a simple solution to locate and connect to an OOo instance is now available as "Simple Bootstrap," check out <http://udk.openoffice.org/common/man/spec/transparentofficecomponents.html>.
-Stephan
Thanks, Mike
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
