Hi All,

I was trying to start OSGI client for version 0.9.0 beta 1 inside Karaf and 
apache Felix, I trying to resolve dependencies using springsource bundle 
resources but I couldn't obtain a system that starts and responds to a 
getContentChanges.

Server that I use for test are based on FileServer non-OSGI that comes with 
0.9.0 beta 1 distribution but as you could see in following stacktrace the 
server didn't receive any communication from client because client couldn't 
resolve spi provider.

Then my question is if anyone of you has a project running with OSGI client and 
could pass me the exact dependencies that you use or redirect me to any source 
where I could find it.

Currently I has a OSGI environment with only that bundles:

[  58] [Active     ] [            ] [   80] CMIS Client OSGI (1.0.0)
[  59] [Active     ] [            ] [   80] OpenCMIS OSGi Client Wrapper 
(0.9.0.beta-1)
[  77] [Active     ] [            ] [   80] Fast Infoset (1.2.2)
[  78] [Active     ] [            ] [   80] Java Activation API (1.1.1)
[  79] [Active     ] [            ] [   80] Extended StAX API (1.0.0)
[  81] [Installed  ] [            ] [   80] Java API for XML Web Services 
(JAX-WS) Reference Implementation (2.1.3)
[  84] [Active     ] [            ] [   80] Java Architecture for XML Binding 
(JAXB) Implementation (2.2.0)
[  85] [Installed  ] [            ] [   80] Java Architecture for XML Binding 
(JAXB) Compile (2.2.0)

And obtained error trying to start bundle 85 with error
Error executing command: Error starting bundles:
                Unable to start bundle 85: Unresolved constraint in bundle 
com.springsource.com.sun.tools.xjc [85]: Unable to resolve 85.0: missing 
requirement [85.0] osgi.wiring.package; 
(&(osgi.wiring.package=com.sun.xml.bind.serializer)(version>=2.2.0)(version<=2.2.0))

I also tried a lot of combinations of JAXB and JAX-WS from springsource but 
with similar results.

If I try to run the test with that status of configuration I obtain that error:

07.06.2013 00:00:05 ERROR [Thread-139] (CmisCrawler:354) 
Error:javax.xml.ws.spi.FactoryFinder$ConfigurationError: Provider 
org.apache.axis2.jaxws.spi.Provider not found
javax.xml.ws.spi.FactoryFinder$ConfigurationError: Provider 
org.apache.axis2.jaxws.spi.Provider not found
        at javax.xml.ws.spi.FactoryFinder$2.run(FactoryFinder.java:135)
        at javax.xml.ws.spi.FactoryFinder.doPrivileged(FactoryFinder.java:273)
        at javax.xml.ws.spi.FactoryFinder.newInstance(FactoryFinder.java:122)
        at javax.xml.ws.spi.FactoryFinder.access$200(FactoryFinder.java:42)
        at javax.xml.ws.spi.FactoryFinder$3.run(FactoryFinder.java:264)
        at javax.xml.ws.spi.FactoryFinder.doPrivileged(FactoryFinder.java:273)
        at javax.xml.ws.spi.FactoryFinder.find(FactoryFinder.java:165)
        at javax.xml.ws.spi.Provider.provider(Provider.java:39)
        at javax.xml.ws.Service.<init>(Service.java:36)
        at 
org.apache.chemistry.opencmis.commons.impl.jaxb.DiscoveryService.<init>(DiscoveryService.java:42)
        at 
org.apache.chemistry.opencmis.client.bindings.spi.webservices.AbstractPortProvider.initServiceObject(AbstractPortProvider.java:240)
        at 
org.apache.chemistry.opencmis.client.bindings.spi.webservices.AbstractPortProvider.getPortObject(AbstractPortProvider.java:184)
        at 
org.apache.chemistry.opencmis.client.bindings.spi.webservices.AbstractPortProvider.getDiscoveryServicePort(AbstractPortProvider.java:115)
        at 
org.apache.chemistry.opencmis.client.bindings.spi.webservices.DiscoveryServiceImpl.getContentChanges(DiscoveryServiceImpl.java:56)
        at 
com.hpexstream.lal.crawler.CmisCrawler.checkStatus(CmisCrawler.java:341)
        at com.hpexstream.lal.crawler.CmisCrawler.run(CmisCrawler.java:152)


Thanks a lot,


Ignasi González
Project Manager
Hewlett-Packard Consultoría y Aplicaciones, S.L.

+34 93 401 9263 / Tel
+34 61 968 3362 / Mobile
[email protected]<mailto:[email protected]>/ Email
Camí de Can Graells  1-21
Sant Cugat del Vallès 08174 Barcelona,  Spain

[hp]<http://www.hp.com/>
Please consider the environment before printing this email.

Reply via email to