Hi Oliver,

thank you *very* much for your hint and pointer!

Unfortunately, I have not found a means to get the class registered. Do
I have to explicitly name that class to register in the
"META_INF/manifest.xml" (and if so, how would that be done)? Currently
the "META-INF/MANIFEST.MF" contains the appropriate entry
("RegistrationClassName:
com.sun.star.script.framework.provider.oorexx.ScriptProviderForooRexx").


On 25.07.2010 19:19, Oliver Brinzing wrote:
>> Is there something I must also denote in the "description.xml" file to
>>     
> you need a "META-INF\manifest.xml" where you list all your files, for example:
>   
... cut (thank you very much for that very helpful snippet!) ...

> http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/File_Format
>   
Thank you very much for this link as well!

Here is my current, timid "manifest.xml", which does not cause the
"RegistrationClassName" to be followed:

    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE manifest:manifest PUBLIC "-//OpenOffice.org//DTD Manifest 
1.0//EN" "Manifest.dtd">
     <manifest:manifest xmlns:manifest="http://openoffice.org/2001/manifest";>

         <manifest:file-entry manifest:full-path="%origin%" 
manifest:media-type="application/vnd.sun.star.uno-component;type=Java" />

    </manifest:manifest>
      

Did leave out the "manifest:full-path" attribute to no avail, using "."
instead of "%origin%" or using "ScriptProviderForooRexx.oxt" would not
make a change. Supplying the name of the jar-file itself did not help
either.


Running "unopkg list --shared" copyin and pasting the information about
that oxt gives:

    Identifier: org.oorexx.uno-via-BSF4ooRexx
      Version: 4.04
      URL: 
vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/F.tmp_/ScriptProviderForooRexx.oxt
      is registered: n/a
      Media-Type: application/vnd.sun.star.package-bundle
      Description: This extension to OpenOffice.org (OOo) adds the easy to 
learn,
    yet powerful scripting language "Open Object Rexx (ooRexx)".
    As a result it becomes possible to add and deploy macros programmed
    in ooRexx from within OOo.

        ooRexx:        http://www.ooRexx.org
        BSF4ooRexx: http://wi.wu.ac.at/rgf/rexx/bsf4oorexx/current/

      bundled Packages: {
        <none>
      }
      

Greatful for any further hints/suggestions!

---rony


Reply via email to