Hi Pierre,
thanks a lot for sharing this info...
best regards,
Cristiano
On 27/05/13 10:46, Pierre De Rop wrote:
Hi Christiano,
I think that Felix was talking about adding the following property in your
framework conf/config.properties:
org.osgi.framework.system.packages.extra=org.w3c.dom.traversal;
version="..."
You can refer to
http://felix.apache.org/documentation/subprojects/apache-felix-framework/apache-felix-framework-configuration-properties.html
Now, I also faced in the past the same kind of problem you are facing, and
what you described in your previous mail is also an option: you can package
the api
in a fragment, as an extension bundle, but I think the system bundle is
"system.bundle":
Fragment-Host: system.bundle;extension:=framework
You can possibly refer to the following post, which might help you (see
solution "A: extension bundle"):
http://blog.springsource.org/2009/01/19/exposing-the-boot-classpath-in-osgi/
hope this helps;
/Pierre
On Mon, May 27, 2013 at 2:48 PM, Cristiano Gavião <[email protected]>wrote:
Hi Felix,
are you talking about to drop org.apache.servicemix.specs.**jaxp-api-1.4,
create a bundle fragment with the head below and expose the
org.w3c.dom.traversal package from JDK?
*Fragment-Host: org.eclipse.osgi;extension:=**framework*
Btw, the interesting fact is that I could run the same test [1] with same
bundles at Equinox :/
this should mean that Equinox don't export any XML package from JDK, right?
[1] - https://github.com/jbehave/**jbehave-osgi/blob/master/**
jbehave-osgi-examples/trader-**felix-pomfirst-paxexam/org.**
jbehave.osgi.examples.trader.**pomfirst.paxexam/src/test/**
java/org/jbehave/osgi/**examples/trader/pomfirst/**paxexam/embedder/**
TraderEmbedderOsgiForPaxExam.**java<https://github.com/jbehave/jbehave-osgi/blob/master/jbehave-osgi-examples/trader-felix-pomfirst-paxexam/org.jbehave.osgi.examples.trader.pomfirst.paxexam/src/test/java/org/jbehave/osgi/examples/trader/pomfirst/paxexam/embedder/TraderEmbedderOsgiForPaxExam.java>
best regards,
Cristiano
On 27/05/13 02:44, Felix Meschberger wrote:
Hi
Looks like you have a conflict on your platform (and yes, this DOM stuff
is nasty, as is all XML, unfortunately)
If your Java Platform provides the org.w3c.dom.traversal package, you
might want to expose it through the system bundle using the
org.osgi.framework.system.**packages.extra framework property
Regards
Felix
Am 27.05.2013 um 05:24 schrieb Cristiano Gavião:
Hello,
I'm trying to use
mvn:org.apache.servicemix.**bundles/org.apache.servicemix.**
bundles.freemarker/2.3.19_1
When I used it alone I got this error:
ERROR: Bundle org.apache.servicemix.bundles.**freemarker [16] Error
starting
mvn:org.apache.servicemix.**bundles/org.apache.servicemix.**
bundles.freemarker/2.3.19_1
(org.osgi.framework.**BundleException: Unresolved constraint in bundle
org.apache.servicemix.bundles.**freemarker [16]: Unable to resolve 16.0:
missing requirement [16.0] osgi.wiring.package;
(osgi.wiring.package=org.w3c.**dom.traversal))
org.osgi.framework.**BundleException: Unresolved constraint in bundle
org.apache.servicemix.bundles.**freemarker [16]: Unable to resolve 16.0:
missing requirement [16.0] osgi.wiring.package;
(osgi.wiring.package=org.w3c.**dom.traversal)
at
org.apache.felix.framework.**Felix.resolveBundleRevision(**
Felix.java:3974)
at org.apache.felix.framework.**Felix.startBundle(Felix.java:**2037)
at
org.apache.felix.framework.**Felix.setActiveStartLevel(**Felix.java:1291)
at
org.apache.felix.framework.**FrameworkStartLevelImpl.run(**
FrameworkStartLevelImpl.java:**304)
at java.lang.Thread.run(Thread.**java:722)
So, I search for a bundle that provides that package:
org.apache.servicemix.specs.**jaxp-api-1.4. But now I'm get this error:
ERROR: Bundle org.apache.servicemix.bundles.**freemarker [16] Error
starting
mvn:org.apache.servicemix.**bundles/org.apache.servicemix.**
bundles.freemarker/2.3.19_1
(org.osgi.framework.**BundleException: Uses constraint violation. Unable
to resolve bundle revision org.apache.servicemix.bundles.**freemarker
[16.0] because it is exposed to package 'org.w3c.dom' from bundle
revisions org.apache.servicemix.specs.**jaxp-api-1.4 [17.0] and
org.apache.felix.framework [0] via two dependency chains.
Chain 1:
org.apache.servicemix.bundles.**freemarker [16.0]
import: (osgi.wiring.package=org.w3c.**dom)
|
export: osgi.wiring.package=org.w3c.**dom
org.apache.servicemix.specs.**jaxp-api-1.4 [17.0]
Chain 2:
org.apache.servicemix.bundles.**freemarker [16.0]
import: (osgi.wiring.package=javax.**swing.tree)
|
export: osgi.wiring.package=javax.**swing.tree; uses:=org.w3c.dom
export: osgi.wiring.package=org.w3c.**dom
org.apache.felix.framework [0])
could someone point me any way to handle this conflict?
thanks,
Cristiano
------------------------------**------------------------------**---------
To unsubscribe, e-mail:
users-unsubscribe@felix.**apache.org<[email protected]>
<mailto:users-**[email protected]<[email protected]>
For additional commands, e-mail: [email protected]<**mailto:
users-help@felix.**apache.org <[email protected]>>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
