Re: [dev] A few brief questions ad extension packages (Re: [dev] Class-Path Entry in Manifest Package File and the Location of the Respective jars?

Hi there, sorry, was off for a week witohut access to e-mail, hence my late answer (keeping the quotings so only this e-mail is needed). Stephan Bergmann wrote: Rony G. Flatscher wrote: Hi Stephan, , in the case of the ooRexx scripting engine: * there is a platform dependent DLL/so

Re: [dev] A few brief questions ad extension packages (Re: [dev] Class-Path Entry in Manifest Package File and the Location of the Respective jars?

Stephan Bergmann wrote: Rony G. Flatscher wrote: Hi Stephan, Feel free to come back here with any questions along your way, Thank you very much for your kind offer! Indeed, after studying your information there would be a couple of questions: * where would one find the full definition

Re: [dev] A few brief questions ad extension packages (Re: [dev] Class-Path Entry in Manifest Package File and the Location of the Respective jars?

Rony G. Flatscher wrote: Hi Stephan, thank you very much for your answers! ... cut ... * ad application/vnd.sun.star.uno-component;type=native: No, such files are not put on any path. If those libraries are UNO libraries that support services/singletons, they will be found by the UNO

Re: [dev] A few brief questions ad extension packages (Re: [dev] Class-Path Entry in Manifest Package File and the Location of the Respective jars?

Rony G. Flatscher wrote: Hi Stephan, thank you very much for your answers! ... cut ... * ad application/vnd.sun.star.uno-component;type=native: No, such files are not put on any path. If those libraries are UNO libraries that support services/singletons, they will be found by the UNO

Re: [dev] A few brief questions ad extension packages (Re: [dev] Class-Path Entry in Manifest Package File and the Location of the Respective jars?

Rony G. Flatscher wrote: Hi Stephan, , in the case of the ooRexx scripting engine: * there is a platform dependent DLL/so which needs to be accessible (at the moment I copy it into OOoHome/program), so the library is *not* an UNO-component, just a native library, * there

Re: [dev] Class-Path Entry in Manifest Package File and the Location of the Respective jars?

Rony G. Flatscher wrote: Hi Stephan, thank you *very* much for your hints and pointers, which I need to follow and study in full in order to be able to experiment with it! (Will take some time, though.) If the three additional jars (bsf-v242-20070128.jar, bsf-rexx-engine.jar, oorexx-uno.jar)

[dev] A few brief questions ad extension packages (Re: [dev] Class-Path Entry in Manifest Package File and the Location of the Respective jars?

Hi Stephan, Feel free to come back here with any questions along your way, Thank you very much for your kind offer! Indeed, after studying your information there would be a couple of questions: * where would one find the full definition for manifest.xml and a list of valid

Re: [dev] A few brief questions ad extension packages (Re: [dev] Class-Path Entry in Manifest Package File and the Location of the Respective jars?

Rony G. Flatscher wrote: Hi Stephan, Feel free to come back here with any questions along your way, Thank you very much for your kind offer! Indeed, after studying your information there would be a couple of questions: * where would one find the full definition for manifest.xml and a

Re: [dev] A few brief questions ad extension packages (Re: [dev] Class-Path Entry in Manifest Package File and the Location of the Respective jars?

Hi Stephan, thank you very much for your answers! ... cut ... * ad application/vnd.sun.star.uno-component;type=native: No, such files are not put on any path. If those libraries are UNO libraries that support services/singletons, they will be found by the UNO framework via the

Re: [dev] Class-Path Entry in Manifest Package File and the Location of the Respective jars?

[Changed the structure of the quoted mail so that my inline answers are in a logical order:] Rony G. Flatscher wrote: Hi there, for finalizing a package for bridging ooRexx with OOo (UNO) I was able to create a package that can be deployed successfully with unopkg add --shared

Re: [dev] Class-Path Entry in Manifest Package File and the Location of the Respective jars?

Hi Stephan, Rony, Stephan Bergmann a écrit : That way, your functionality (a script provider for ooRexx) comes as a self-contained entity (that can be deployed in one step via unopkg or OOo's Tools - Extension Manager...), without the need to add additional jars to special places (OOo's

Re: [dev] Class-Path Entry in Manifest Package File and the Location of the Respective jars?

Hi Stephan, thank you *very* much for your hints and pointers, which I need to follow and study in full in order to be able to experiment with it! (Will take some time, though.) If the three additional jars (bsf-v242-20070128.jar, bsf-rexx-engine.jar, oorexx-uno.jar) are only needed by

Re: [dev] Class-Path Entry in Manifest Package File and the Location of the Respective jars?

Bonsoir Cedric, Stephan Bergmann a écrit : That way, your functionality (a script provider for ooRexx) comes as a self-contained entity (that can be deployed in one step via unopkg or OOo's Tools - Extension Manager...), without the need to add additional jars to special places (OOo's

[dev] Class-Path Entry in Manifest Package File and the Location of the Respective jars?

Hi there, for finalizing a package for bridging ooRexx with OOo (UNO) I was able to create a package that can be deployed successfully with unopkg add --shared ScriptProviderForooRexx.jar The scripting language is registered and shows up in the Macro menu. In order to ease installation

Re: [dev] Class-Path Entry in Manifest Package File and the Location of the Respective jars?

Hi there, just a small update to my little (still open!) question: copying the jar-files listed on Class-Path to the same directory the OOo package installer chose to install the jar file containing that Class-Path entry will allow to find those jar files. Now, if I knew upfront where the OOo