Please, make vboxjws.jar an OSGi bundle => fixed in svn

[ludo]

Hi, we are using vboxjws.jar client WS java jar in an OSGi environment (i.e GlassFish application). It would be nice if this jar would be out of the box a OSgi module. To achieve that, it is very easy: you only need to modify the manifest file to expose import/export information. This is what is working for us:

Manifest-Version: 1.0 Export-Package: org.virtualbox_4_0;uses:="javax.xml.ws.spi,javax.jws,j

avax.xml.ws.wsaddressing,javax.xml.parsers,javax.xml.transform.dom,or g.w3c.dom,org.xml.sax,javax.xml.namespace,javax.xml.ws.http,javax.xml .ws.handler,javax.jws.soap,javax.xml.bind.helpers,javax.xml.bind.atta chment,javax.xml.stream,javax.xml.transform,javax.xml.bind.annotation ,javax.xml.bind.util,javax.xml.transform.stream,javax.xml.bind,javax. xml.ws,javax.xml.ws.soap";version="4.0.4"

Implementation-Title: vboxjws Implementation-Version: 4.0.4 Specification-Vendor: VirtualBox Community Bundle-Name: vboxjws Bundle-Vendor: VirtualBox Community Implementation-Vendor: VirtualBox Community Bundle-Version: 4.0.4 Build-Jdk: 1.6.0_24 Bnd-LastModified: 1299787919093 Bundle-ManifestVersion: 2 Bundle-License: ​https://glassfish.dev.java.net/nonav/public/CDDL+GPL.h

tml

Import-Package: javax.validation.constraints;version="1.0",javax.jws,c

om.sun.xml.ws.developer,com.sun.xml.ws,com.sun.xml.ws.api.message,jav ax.jws.soap,javax.xml.namespace,javax.xml.ws,javax.xml.ws.spi,javax.x ml.ws.soap,javax.xml.ws.handler,javax.xml.ws.http,javax.xml.ws.wsaddr essing,javax.xml.parsers,javax.xml.stream,javax.xml.transform,javax.x ml.transform.dom,javax.xml.transform.stream,org.w3c.dom,org.xml.sax,j avax.xml.bind,javax.xml.bind.annotation,javax.xml.bind.attachment,jav ax.xml.bind.helpers,javax.xml.bind.util,org.virtualbox_4_0;version="3 .1"

Bundle-SymbolicName: org.virtualbox_4_0 Originally-Created-By: 11.0-b16 (Sun Microsystems Inc.) Extension-Name: vboxjws Archiver-Version: Plexus Archiver

The need for importing com.sun classes is due to a JAX-WS bug/limitation.. We spent a lof of time to figure this out. If you use these manifest.mf entries, then this jar becomes an OSgi bundle usable in all OSGi envs (Eclipse, GlassFish, etc etc)

[Klaus Espenlaub]

Done in current trunk, decision whether this will be backported to 4.1 and earlier is pending.