Oh, wow. How long has this bundle been out? Better late than never, I guess.
I suppose I'll have to use the proprietary headers for now, unless you guys can have this fixed by next week! FYI, what I'm working on is a plugin for Cytoscape 3.0.x, which uses an old (pre-2.3) version of Karaf. By the way, about providers: does the file in resources/services have to point at an implementation class contained WITHIN the provider bundle? Or can it point at any class whatsoever? On Wed, Feb 5, 2014 at 4:44 PM, David Bosschaert <[email protected] > wrote: > Hi Tovi, > > I had a quick look, and found that the static weaving does work for > bundles that use the Aries 'proprietary' SPI-Consumer headers. To see > this in action, you can try it with the spi-fly-example-client1-bundle > example. > > I noticed that the static weaving is not working with bundles that use > the Require-Capability/spec compliant metadata and filed ARIES-1156 > for that. > > You are right that it should be possible for one bundle to be both the > provider and consumer. I found out that this currently doesn't work > and created ARIES-1157 for that. > > Cheers, > > David > > On 4 February 2014 19:59, Tovi Almozlino <[email protected]> wrote: > > Hi there, > > > > 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 > > generating. > > > > 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 > > com.sun.xml.internal.ws.spi.ProviderImpl 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. > > > > Any advice? >
