Sorry for jumping in late to this thread, but I'm glad you got it to work :) Just to confirm, under normal conditions, CXF/DOSGi doesn't require any Java annotation on your service to make it available as a Web Service. Setting the service registration properties should be enough.
One thing to note is that quite a number of fixes went in to CXF/DOSGi since its 1.0 release. Specifically a number of fixes that apply to using it from Declarative Services, which may also be applicable to iPOJO usage. So the best thing is to try CXF/DOSGi 1.1-SNAPSHOT if you're having problems with 1.0. We have to wait for CXF 2.2.3 to be released before we can release CXF/DOSGi 1.1. Hopefully this will happen in August... Cheers, David 2009/7/2 Clement Escoffier <[email protected]>: > > On 01.07.2009, at 20:02, Richard S. Hall wrote: > >> On 7/1/09 1:39 PM, Clement Escoffier wrote: >>> >>> Last things, to work I started two gateway: >>> - Felix 1.8.1 with iPOJO, Compendium, CXF (Snapshot) single bundle, >>> AdderServiceInterface and AdderServiceProvider >>> - Equinox 3.5 with iPOJO, OSGi service, OSGi Utils, CXF (Snapshot) single >>> bundle, AdderServiceInterface, AdderServiceImporter and AdderServiceConsumer >>> >>> For some strange reason, I was not able to import the service from >>> Felix... Maybe a detail of CXF that I ignore. equinox 3.5 is required as CXF >>> relies on ServiceHooks. >> >> Felix has implemented the service hooks needed by CXF for a little while >> now, I think. Trunk has full support, although I have some outstanding >> patches to commit for the TCK. > > Good news. > It works on the latest Felix trunk ! > > Regards, > > Clement > > >> >> -> richard >> >>> >>> Regards, >>> >>> Clement >>> >>> On 30.06.2009, at 20:41, Joel Schuster wrote: >>> >>>> Great, thanks! >>>> >>>> I can't get it to work at all. This actually may be more a question then >>>> for the CXF people, just let me know. I'm not sure which properties to set. >>>> Based on what you see on those links I referred to, @ServiceProperty is the >>>> correct annotation to use, right? >>>> >>>> Do you know of a single bundle solution that iPojo integrates easily >>>> with? I'd like to just provide a simple annotation or config property and >>>> have it just make my service available automatically. >>>> >>>> Why did you make the decision to write your own? >>>> >>>> - Joel >>>> >>>>> -----Original Message----- >>>>> From: Bourret Pierre [mailto:[email protected]] >>>>> Sent: Tuesday, June 30, 2009 9:54 AM >>>>> To: [email protected] >>>>> Subject: Re: iPojo as WebService >>>>> >>>>> Hi Joel. >>>>> >>>>> I'm daily using iPOJO service as web services. I don't use CXF but a >>>>> home-made Distributed Service implementation. However, it should be >>>>> very >>>>> similar. >>>>> >>>>> Feel free to ask me if you encounter any issue. >>>>> >>>>> -- >>>>> Pierre Bourret >>>>> >>>>> >>>>> 2009/6/30 Joel Schuster <[email protected]> >>>>> >>>>>> I'd like to expose my iPojo as a WebService. >>>>>> >>>>>> I'm using the Distributed OSGi single bundle from apache cxf: >>>>>> http://cxf.apache.org/distributed-osgi.html >>>>>> >>>>>> Based on what I read, (http://cxf.apache.org/dosgi-ds-demo-page.html) >>>>>> theoretically I should be able to take a working iPojo based service >>>>>> and >>>>> >>>>> add >>>>>> >>>>>> add a few @ServiceProperties and deploy a .cfg file with FileInstall >>>>> >>>>> bundle: >>>>>> >>>>>> osgi.remote.interfaces=* >>>>>> osgi.remote.configuration.type=pojo >>>>>> >>>>> >>>>> osgi.remote.configuration.pojo.address=http://localhost:9090/mypojoservice >>>>>> >>>>>> Has anyone tried this or something similar without having to add the >>>>>> overhead of going all the way to ServiceMix? >>>>>> >>>>>> Any help would be appreciated. >>>>>> >>>>>> - Joel >>>>>> >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: [email protected] >>>>>> For additional commands, e-mail: [email protected] >>>>>> >>>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
