Hi,
Yes, of course. In this case you will probalby not need a "real" Java Bean, with bean info and stuff, in this case you most likely can use OOoBean as it is. You just have to make sure that it can find soffice and its jar files, e.g. by having the class files where they belong (under program/classes) and having them in your CLASSPATH. Or your class loader has to make sure it can find them, and soffice.
OK, things cleared up a little. You won't be able to use CLASSPATH when you deploy your app in a JAR anyway, so either you have a classloader, or you don't ship JARs (or you use the transparent classloader?).
If you had your app in a JAR IMHO even adding the classpath of the office installation (suppose you know where your client keeps his office) in the manifest would fail because officebean.jar looked in the wrong directory for libofficebean.so, or am I missing something here?
I always thought that adding the class path to your manifest would be sufficient and has the same effect than using the cp-commandline switch but I could be completely mistaken.
I thought a MANIFEST like this would work:
------------------8<------------------ Manifest-Version: 1.0 Main-Class: at/bestsolution/oeush/members/MembersAdmin Class-Path: lib/a.jar /usr/lib/openoffice/program/classes/officebean.jar ... ------------------8<------------------
Besides, a (nontransparent) classloader is still a issue for me, there is no example out there, is there?
bye, 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]
