I think it's better in general to use the multi-bundle distribution. The single-bundle distro is really only good to get started, but I would not recommend using it in real scenarios.
If there is an issue with the multi-bundle distro it's worth figuring out what it is. In this case apparently a bundle is looking for javax.transaction.xa. Note that this package is actually (partly) provided through the JRE. Adding it to the org.osgi.framework.system.packages.extra property might help. Best regards, David On 17 October 2012 16:33, Marco Speranza <[email protected]> wrote: > Hi, > > yes I've already tried to move to multi-bundle distro. when I install > the distro directly into apache felix it works fine. > but when I try to install the distro into apache karaf it throws this > exception: > > Error executing command: Could not start bundle > file:apache-cxf-dosgi-ri-1.3.1/dosgi_bundles/cxf-bundle-minimal-2.5.2.jar > in feature(s) cxf-dosgi-1.3.1: Unresolved constraint in bundle > org.apache.cxf.bundle-minimal [91]: Unable to resolve 91.0: missing > requirement [91.0] package; (package=javax.transaction.xa) > > thank in advance > > > > -- > Marco Speranza <[email protected]> > Google Code: http://code.google.com/u/marco.speranza79/ > > > 2012/10/17 Sergey Beryozkin <[email protected]>: >> Hi >> >> On 17/10/12 16:17, Marco Speranza wrote: >>> >>> Hi all, >>> >>> I'm trying to install cxf distributed osgi (the single bundle release) >>> into apache karaf configured with felix container. >>> >>> I tried to start 'cxf-dosgi-ri-samples-greeter-rest' sample but I >>> experienced this error: >>> >>> Exception in thread "pool-7-thread-5" >>> org.osgi.framework.ServiceException: CXF DOSGi: No HTTP Service could >>> be found to publish CXF endpoint in. >>> at >>> org.apache.cxf.dosgi.dsw.handlers.HttpServiceConfigurationTypeHandler.getHttpService(HttpServiceConfigurationTypeHandler.java:248) >>> at >>> org.apache.cxf.dosgi.dsw.handlers.HttpServiceConfigurationTypeHandler.registerServletAndGetBus(HttpServiceConfigurationTypeHandler.java:199) >>> at >>> org.apache.cxf.dosgi.dsw.handlers.JaxRSHttpServiceConfigurationTypeHandler.createServer(JaxRSHttpServiceConfigurationTypeHandler.java:56) >>> at >>> org.apache.cxf.dosgi.dsw.service.RemoteServiceAdminCore.exportService(RemoteServiceAdminCore.java:247) >>> at >>> org.apache.cxf.dosgi.dsw.service.RemoteServiceAdminInstance$1.run(RemoteServiceAdminInstance.java:72) >>> at >>> org.apache.cxf.dosgi.dsw.service.RemoteServiceAdminInstance$1.run(RemoteServiceAdminInstance.java:66) >>> at java.security.AccessController.doPrivileged(Native Method) >>> at >>> org.apache.cxf.dosgi.dsw.service.RemoteServiceAdminInstance.exportService(RemoteServiceAdminInstance.java:66) >>> at >>> org.apache.cxf.dosgi.dsw.service.RemoteServiceAdminInstance.exportService(RemoteServiceAdminInstance.java:38) >>> at >>> org.apache.cxf.dosgi.topologymanager.TopologyManager$2.run(TopologyManager.java:265) >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) >>> at java.lang.Thread.run(Thread.java:680) >>> >>> >>> >>> could anyone help me to fix it and start correctly the sample? >> >> >> It is a known issue - HTTP service can only be bound to from a multi-bundle >> distro. I've briefly looked into this issue before, made sure as far as I >> recall that all the individual bundle activators are called from a single >> distro activator, but did not have any luck at a time. >> >> Can you move to a multi bundle distro ? Or may be investigate the issue >> further - it is something to do with the order in which bundles are >> activated, something like that >> >> Sergey >> >> >>> >>> thank in advance >>> >>> -- >>> Marco Speranza<[email protected]> >>> Google Code: http://code.google.com/u/marco.speranza79/ >> >> >> >> -- >> Sergey Beryozkin >> >> Talend Community Coders >> http://coders.talend.com/ >> >> Blog: http://sberyozkin.blogspot.com
