Hendy Irawan wrote:
On Mon, Dec 1, 2008 at 3:18 PM, Freeman Fang <[EMAIL PROTECTED]> wrote:
Hendy Irawan wrote:
I guess because jsr311-osgi-api doesn't have correct imports, but then
again, if CXF doesn't provide nor endorse a particular jsr311-api
artifact, how would we know its "correctness"? More convoluted than
standard Java, manifest.mf can make or break a OSGi bundle.
...and the entire app for that matter
I've reported an issue regarding jsr311-api and CXF here:
https://issues.apache.org/jira/browse/CXF-1929
I think we need add a jsr-311 api bundle in servicemix.
Create a ticket [1] to track it
[1]https://issues.apache.org/activemq/browse/SMX4-167
Since SMX4-167 is done, could you try this jsr311-api bundle?
We just hack FactoryFinder.java from jsr311 api to delegate the spiClass
finding to OsgiLocatoer(this is also a general solution for spiClass
finding in osgi env for other apis, like saaj, stax, etc) when in OSGI
env, I think you needn't embed jsr311 api in your application bundle now.
Freeman
Regards
Freeman
Thanks, noted with respect. :)
