The major differences is that the specification bundles from ServiceMix have been enhanced to discover the implementation bundle. If you use a plain bundle for the api, the client bundle (the one using jaxb) has to have the needed META-INF/services entry available in the classloader. This can be achieved by using an Require-Bundle on the implementation of jaxb. ServiceMix specifications bundles have all been enhanced to overcome this requirement and be able to keep the client bundle independant from the implementation used: the only requirement is to have an Import-Package on the javax.xml.bind packages.
2009/3/16 Oisin Hurley <[email protected]> > > As you will see, we use the jaxb spec & jaxb-impl implementation : > > > > > <bundle>mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jaxb-impl/2.1.6_1</bundle> > > > > > <bundle>mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.jaxb-api-2.1/1.2.0</bundle> > > It would be interesting to see what the difference is between the > servicemix instance of these bundles and the Springsource instance. > > BTW Renat there are now versions of StAX, JAXB, JAXWS and > activation available from Eclipse Orbit, if that is useful in any way. > > --oh > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
