I'm trying to get an OSGI bundle that uses JAX-WS (which uses
ServiceLoader) working in an OSGI 4.2 framework.
It seems that the SPI Fly Static Weaving command line tool generates a
Manifest file that the Static Weaving runtime bundle doesn't know how to
read. Specifically, the bundle seems to be looking for hash signs (#) in
the Manifest's Require-Capability header which the tool is definitely not
I tried editing them in manually, and although the bundle did accept the
edited Manifest, the weaving did not seem to work.
I'm pointing it at the javax.xml.ws.spi.Provider interface and the
implementation, although I'm not sure about that last one. I'd also prefer
that my bundle be both a "Consumer" AND a "Provider" (with the appropriate
file in its resources/services directory), which I'm not entirely sure is
okay, although I don't see why it couldn't be.