Hi Charles, If they're not explicitly exlcuded by karaf, in Java6 the javax.xml.ws etc. packages will be pulled in from the JRE rt.jar as system packages.
This causes no end of trouble on Equinox, as system packages are assigned the version "0.0" whereas many bundles with a dependency on javax.xml.wsetc. will version constrain the Import-Package entry, for example with something like "[2.1.0,3.0.0)". This would lead to a conflict at bundle resolution time. Once exlcuded from the system packages, these javax.* packages can instead be pulled in with an appropriate version from the corresponding specs bundle. Cheers, Eoghan On 19 February 2010 12:48, Charles Moulliard <[email protected]> wrote: > Hi, > > Why the packages javax.*,org.w3c.*,org.xml.* are not versioned in > Servicemix > 4.x / Fuse 4.2 ? > > ka...@root> packages:exports 0 > > System Bundle (0): com.sun.org.apache.xalan.internal.xsltc.trax; > version=0.0.0 > System Bundle (0): com.sun.org.apache.xerces.internal.dom; version=0.0.0 > System Bundle (0): com.sun.org.apache.xerces.internal.jaxp; version=0.0.0 > System Bundle (0): com.sun.org.apache.xerces.internal.xni; version=0.0.0 > System Bundle (0): com.sun.jndi.ldap; version=0.0.0 > System Bundle (0): javax.accessibility; version=0.0.0 > System Bundle (0): # javax.activation; version=0.0.0 > System Bundle (0): javax.activity; version=0.0.0 > System Bundle (0): # javax.annotation; version=0.0.0 > System Bundle (0): # javax.annotation.processing; version=0.0.0 > System Bundle (0): javax.crypto; version=0.0.0 > System Bundle (0): javax.crypto.interfaces; version=0.0.0 > System Bundle (0): javax.crypto.spec; version=0.0.0 > System Bundle (0): javax.imageio; version=0.0.0 > System Bundle (0): javax.imageio.event; version=0.0.0 > System Bundle (0): javax.imageio.metadata; version=0.0.0 > System Bundle (0): javax.imageio.plugins.bmp; version=0.0.0 > System Bundle (0): javax.imageio.plugins.jpeg; version=0.0.0 > System Bundle (0): javax.imageio.spi; version=0.0.0 > System Bundle (0): javax.imageio.stream; version=0.0.0 > > Because of that we have unresolved dependencies errors when we generate a > MANIFEST file using the version 1.4 of maven-bundle-plugin where the > version > of the package is added > > Kind regards, > > Charles Moulliard > Senior Enterprise Architect > Apache Camel Committer > > ***************************** > blog : http://cmoulliard.blogspot.com > twitter : http://twitter.com/cmoulliard > Linkedlin : http://www.linkedin.com/in/charlesmoulliard > > Apache Camel Group : > http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm >
