On 07/12/12 11:14, Reto Bachmann-Gmür wrote:
Hi
In general it is good practive in OSGi to import everything you export. but
in this case I guess it could be a private-package to just tie jena to its
preferred xerces bundle.
You're very welcome to submit a patch maybe also updating the jena version
:)
Clerezza uses a non-Apache version of Jena - 2.6.4 (BSD licensed)
Jena uses Xerces v2.10.0 and has for a while (and it drops the need for
ICU4J).
The transactional and robust TDB implementation will keep data safer
than the old version Clerezza is using.
Andy
Cheers,
Reto
On Fri, Dec 7, 2012 at 12:00 PM, Minto van der Sluis <[email protected]> wrote:
Thanks for your reply.
See my remarks below
Regards,
Minto
Op 7-12-2012 11:37, Daniel Spicar schreef:
I am not sure what is happening but it is possible that Xerces is
confused
because it somehow found conflicting class definitions.
Regarding "org.apache.clerezza.ext:com.hp.hpl.jena.tdb":
I don't know why it imports 'xerces.util' but
'org.apache.clerezza.ext:com.hp.hpl.jena.tdb' is an 'osgi-ified' Jena TDB
(presumably an old version). TDB depends on Xerces via Jena Core so I
assume the import comes from somewhere there.
Xerces 2.9.1 is embedded in the 'osgi-fied' bundle. It is also in the
bundle classpath. So if I understand Osgi correctly (I am quite new
there as well) it is not necessary to import the package.
It is possible that when you remove the import everything will still work
but it can not be guaranteed. Maybe somebody who created the TDB bundle
can
remember.
In my simple use case it is possible to parse and store RDF data. But
there might be other use cases that might require the import and/or
export. That's why I send out the request in the first place before
creating and issue. But maybe creating an issue is not a bad idea after
all. The issues can always be closed if this is as designed.
On 6 December 2012 17:54, Minto van der Sluis <[email protected]> wrote:
Why is this bundle both importing and exporting org.apache.xerces.util?
When I remove "org.apache.xerces.util" from both the import-package and
export-package I no longer have the reported error.
--
ir. ing. Minto van der Sluis
Software innovator / renovator
Xup BV
Mobiel: +31 (0) 626 014541
