Jürgen Schmidt wrote:
Hi Jorge,
first of all it isn't a good idea to attach zip files to mails on this
mailing list.
Your package depends on the install order, but the order is not
guaranteed (at least not in a zip file). Your library reads config items
from your xcu file. But as you see in your log file, this xcu file get
installed after the library. Maybe this has worked in the past per chance.
I would assume that when you create a <your_name>.uno.pkg package with
package manifest file (/META-INF/manifest.xml) and take care of the
right order in the manifest file that the current implementation takes
care of this order (i am not 100% sure). Please try your package with
the new package format (the zip format is deprecated) and let me know if
it works.
I will think about your problem and maybe we have to improve the
installation mechanism to guarantee some install order or at least that
config files and rdb are installed before component jars and libs.
If the problem is that the configuration of a component needs to see an
xcu file, then the solution should be easy---change the code of the
component so that its *configuration* parts do not execute code that
needs the xcu (which should always be possible).
-Stephan
example /META-INF/manifest.xml
<?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:media-type="application/vnd.sun.star.configuration-schema"
manifest:full-path="AddonConfiguration.xcs"/>
<manifest:file-entry
manifest:media-type="application/vnd.sun.star.configuration-data"
manifest:full-path="AddonConfiguration.xcu"/>
<manifest:file-entry
manifest:media-type="application/vnd.sun.star.uno-typelibrary;type=RDB"
manifest:full-path="<your_rdb_file>.rdb"/>
<manifest:file-entry
manifest:media-type="application/vnd.sun.star.uno-component;type=Java"
manifest:full-path="<your_comp_jar>.uno.jar"/>
<manifest:file-entry
manifest:media-type="application/vnd.sun.star.uno-component;type=native;platform=Windows"
manifest:full-path="Windows/<your_comp_lib>.uno.dll"/>
</manifest:manifest>
In the manifest file you have to insert all parts of your package which
should be registered. All other not referenced parts are untouched.
See also the DevGuide
(http://api.openoffice.org/docs/DevelopersGuide/Components/Components.xhtml#1_9_Deployment_Options_for_Components)
Juergen
[EMAIL PROTECTED] wrote:
Hi, all!
I've developed a UNO package that works correctly for OOo version 1.5
but whose
intallation on 2.0 fails. The problem seems to be related to a very picky
detail: as the package loads images and dynamic-link libraries of its
own, I
had to customize the configuration of my add-on in order to include a
configuration key granting access to the installation directory (by
the way, is
this any easier now in version 2.0?). I'd most appreciate it if you
could take a
look at the zip file in attachment. There are the error messages I get
during
installation of my package on OOo 2.0 as well as the "problem" xcs and
xcu
files.
Thanks in advance. Cheers,
Jorge.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
