Hi

Jochen Staerk wrote:
Hi,

ooobean is great, I use it in a small project (gnuaccounting.sf.net),
but I have a problem:

my app only works when ooobean.jar is in the classpath. I can't deploy
ooobean.jar with my application because it uses relative paths to  the
installed openoffice. I can't use sth. like a custom OOoconnection
because this would require a started OO instance with a customized config.

1) Is there any way to start a standard openoffice instance (without
changing the config) from  a custom directory, something like like
startOOoConnection('file:///usr/local/lib/ooo-2.0')?
No. The jars should remain in the office installation.The OOoBean will find the soffice based on the location of the jars. Or you have a custom classloader that knows where the office can be found.

2) if not, how hard would it be to patch ooo to support something like
this?  Would one have chances to get this upstream?
If it were only for locating the soffice executable. But the initial problem is how does Java locate the JARs (its not only officebean.jar).Also the officebean.jar must be located first. In the SDK there should be an example of an example of a custom classloader, that can be used by the application and which can then load the officebean, etc.



3) would this violate any design issues, e.g that a ooo 2.0.3 officebean
could or should not connect to 2.0.2 libraries (.so/.dlls)?
Although mixing libraries of different versions may work, it is generally no good idea, because no one can guarantee that it works.And if something fails you do not know if it happens because of a bug or mixing the libs.

4) how else could this be done? As far as I understood a classloader
would be tedious(?), so i currently use a starter. This starter
basically executes java -cp <your openoffice location> mainclass (is
there any way to tell a running jre to change classpath or start another
instance with another cp?) and interestingly is currently the reason why
the windows version of my app does not work.
I would use custom classloader approach.


Joachim



5) I'd like to keep this thing as multiplattform as possible, that's
e.g. the reason why I don't just bundle it with
windows-portableopenoffice....

so: how would you do that?

thanks a lot and kind regards,
Jochen

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to