Rony G. Flatscher wrote:
Hmm,

just to be sure: if I add my jar-file ("oorexx-uno.jar", containing a plain Java-class that itself will access UNO classes) to a package ("ScriptProviderForooRexx.jar") and add the (extension) entry in the package's manifest file:

   Class-Path: oorexx-uno.jar

Would that be sufficient in that all Java-programs that got invoked via the scripting engine can get access to the content of "oorexx-uno.jar"?

Unfortunately, no. You currently cannot easily have one OOo extension (aka "package" or "UNO package") supply a .jar that can be used by other OOo extensions or from OOo scripts (that are not packaged up as OOo extensions); other than adding the .jar to the global classpath via "Tools - Options... - Java."

In the context of OOo extension dependencies, I recently thought about desirable improvements in this area, like having an OOo extension A that states a dependency on an X.jar supplied by OOo extension B. Then, code from extension A could be executed either in a classloader environment where X.jar from B is directly available (this would be the most convenient solution), or in an environment where it can somehow obtain a URL for X.jar, which it would then use to create a URLClassLoader to access classes from X.jar (which would be a rather cumbersome solution).

In that context, I had not yet thought about OOo scripts that are not packaged up as OOo extensions, so thanks for your input.

-Stephan

If not, where could I find infos on how to supply the needed entries in the manifest file for the package?

Regards,

---rony



Kay Ramme - Sun Germany - Hamburg wrote:
Ollie,

Oliver Braun wrote:
All jars files in <jre>/lib/ext are added to the CLASSPATH automatically, having something similar in OOo would be nice.
I am wondering, what the use cases would be. Only think I can come up with is to simplify the development of components (avoiding zipping and installation). The "program/classes" directory is currently an implementation detail only, switching to the URE is going to change the directory structure incompatible. By the way, there is not yet a "user/classes" directory, so that jar files could only be added to the base installation.

I thought that being able to edit the javasettings file would be sufficient.

Regards,
Oliver
Kay

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

Reply via email to