-
Aug 25th, 2008, 05:48 AM
#1
activemq
Wanted to add activemq in order to use jms.
am using s2ap rc1
Created the following library:
Library-SymbolicName: jms
Library-Name: JMS lib
Library-Version: 1.0.0.RELEASE
Import-Bundle:
com.springsource.org.apache.activemq;version="[5.1.0,5.2.0]",
com.springsource.javax.jms;version="[1.1.0,1.3.0]",
com.springsource.javax.management.j2ee;version="[1.0.1,1.3.0]",
com.springsource.javax.ejb;version="[3.0.0,3.3.0]",
com.springsource.javax.servlet;version="[2.5.0,2.6.0]",
com.springsource.javax.xml.rpc;version="[1.1.0,1.3.0]",
com.springsource.javax.xml.soap;version="[1.3.0,1.5.0]",
com.springsource.javax.activation;version="[1.1.1,1.3.0]",
com.springsource.org.apache.commons.logging;versio n="[1.1.1,1.2.0]",
com.springsource.org.apache.xmlcommons;version="[1.3.3,1.5.0]"
including the library into a bundle description (manifest.mf) produces the following error:
Resolver report:
Bundle: mybundy ... - Uses Conflict: Import-Package: org.springframework.remoting.jaxrpc; version="2.5.5.A"
Possible Supplier: org.springframework.web_2.5.5.A - Export-Package: org.springframework.remoting.jaxrpc; version="2.5.5.A"
Possible Conflicts: org.springframework.remoting,javax.servlet,org.aop alliance.intercept,org.springframework.context.sup port,javax.xml.rpc.server,org.springframework.cont ext,javax.xml.rpc.soap,org.springframework.web.con text,javax.xml.rpc,javax.xml.namespace
have not come accross such problem before ...
any idea ???
-
Aug 26th, 2008, 06:16 AM
#2
activemq
It's a bit of a cryptic message I agree (comes from Equinox but we are trying to improve it in a later release, I believe). In the meantime, this is roughly what it means as I understand it: your bundle "mybundy" has introduced a conflict in a "uses" clause. Probably it's a version conflict (they usually are). It means both your bundle and the org.springframework.web have a common dependency which cannot be resolved. The "Possible Conflicts" is a list of packages that tells you where you might be able to find the problem.
It is quite likely that you depend explicitly in your bundle on something (one of the "Possible Conflicts") that is also a dependency of org.springframework.web with a different version.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules