You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by David Bosschaert <da...@gmail.com> on 2010/03/01 16:39:05 UTC
Re: Services provided by DOSGi
Hi Chris,
Not sure about the learning curve but yeah, the underlying data
binding and protocol are dynamically configured using OSGi Service
Properties. If you put the the following service property on your
service it will use SOAP/HTTP:
service.exported.configs=org.apache.cxf.ws
whereas if you put this one on it will use REST/HTTP:
service.exported.configs=org.apache.cxf.rs
no restarts needed :)
so for any other databinding/protocol that we would support in the
future, it would be a matter of defining a config type for it too.
Best regards,
David
On 27 February 2010 16:16, Clark, Chris <ch...@hp.com> wrote:
> Hi
>
> Thx for the reply :-)
>
> So currently SOAP/HTTP and REST/HTTP is supported, I was just wondering about the learning curve involved to support Hessian/Burlap, which also work over HTTP (sure I saw an article bouncing around the internet about it, but can't remember where I saw it).
>
> One thing I was considering was having the exposures dynamically activated, and preconfigured base URLs (so you could for instance via a config service tell DOSGi to turn on one or more of SOAP/HTTP, Hessian/HTTP, Burlap/HTTP, and REST/HTTP bindings, without any restarts or file editing).
>
> Anything I have missed in the current CXF implementation that might be heading in this direction, or are there some big plans for the future ;-)
> Don't want to be reinventing the wheel (even though I seem to be veering
> towards the realms of ESB solutions)
>
> I'm not too crazy about the support for RMI/JMS/etc..., these were just examples, and probably bad ones to supply because of their nature (not based on HTTP), but I can see you know what I generally mean...
>
> Chris Clark
>
> "Audio, Video, Disco"
>
>
> -----Original Message-----
> From: David Bosschaert [mailto:david.bosschaert@gmail.com]
> Sent: Friday, February 26, 2010 11:28 AM
> To: users@cxf.apache.org
> Subject: Re: Services provided by DOSGi
>
> Hi Chris,
>
> Yes, this should be possible. The idea of using OSGi services and then
> distribute them without having to worry about the protocol is exactly
> what we had in mind when developing DOSGi!
> The CXF-DOSGi implementation currently supports: SOAP/HTTP and
> REST/HTTP. They can be configured by setting the org.apache.cxf.ws or
> org.apache.cxf.rs configuration type. If you don't specify a
> configuration type it defaults to org.apache.cxf.ws (SOAP).
>
> Currently these two are supported, there are people talking about
> supporting JMS as well, but it should be possible to add something
> completely different as well... For more information see:
> http://cxf.apache.org/distributed-osgi-reference.html
>
> Best regards,
>
> David
>
> On 25 February 2010 22:09, Clark, Chris <ch...@hp.com> wrote:
>> Hi there,
>>
>> I was just wondering, after struggling to incorporate CXF DOSGI into a long-running 'playground' project of mine, whether it is possible to use the DOSGI system provided with CXF for other front protocols - so can OSGi services be exposed via Hessian/Burlap/RMI/XML-RPC/etc... using this system.
>>
>> The whole idea that I had was that we had a load of OSGi services, but would like to be able to expose them dynamically, without any worry about the front-end protocol (whether it be SOAP/JSON/XML-RPC/Hessian/whatever).
>>
>> Does CXF DOSGI support this? and is there any documentation about it?
>>
>> Chris Clark
>>
>> "Audio, Video, Disco"
>
RE: Services provided by DOSGi
Posted by "Clark, Chris" <ch...@hp.com>.
OK, thanks David :-)
I'll do some more reading on those config types then ...
Thanks all for your feedback :-D
Chris Clark
"Audio, Video, Disco"
-----Original Message-----
From: David Bosschaert [mailto:david.bosschaert@gmail.com]
Sent: Monday, March 01, 2010 4:39 PM
To: users@cxf.apache.org
Subject: Re: Services provided by DOSGi
Hi Chris,
Not sure about the learning curve but yeah, the underlying data
binding and protocol are dynamically configured using OSGi Service
Properties. If you put the the following service property on your
service it will use SOAP/HTTP:
service.exported.configs=org.apache.cxf.ws
whereas if you put this one on it will use REST/HTTP:
service.exported.configs=org.apache.cxf.rs
no restarts needed :)
so for any other databinding/protocol that we would support in the
future, it would be a matter of defining a config type for it too.
Best regards,
David
On 27 February 2010 16:16, Clark, Chris <ch...@hp.com> wrote:
> Hi
>
> Thx for the reply :-)
>
> So currently SOAP/HTTP and REST/HTTP is supported, I was just wondering about the learning curve involved to support Hessian/Burlap, which also work over HTTP (sure I saw an article bouncing around the internet about it, but can't remember where I saw it).
>
> One thing I was considering was having the exposures dynamically activated, and preconfigured base URLs (so you could for instance via a config service tell DOSGi to turn on one or more of SOAP/HTTP, Hessian/HTTP, Burlap/HTTP, and REST/HTTP bindings, without any restarts or file editing).
>
> Anything I have missed in the current CXF implementation that might be heading in this direction, or are there some big plans for the future ;-)
> Don't want to be reinventing the wheel (even though I seem to be veering
> towards the realms of ESB solutions)
>
> I'm not too crazy about the support for RMI/JMS/etc..., these were just examples, and probably bad ones to supply because of their nature (not based on HTTP), but I can see you know what I generally mean...
>
> Chris Clark
>
> "Audio, Video, Disco"
>
>
> -----Original Message-----
> From: David Bosschaert [mailto:david.bosschaert@gmail.com]
> Sent: Friday, February 26, 2010 11:28 AM
> To: users@cxf.apache.org
> Subject: Re: Services provided by DOSGi
>
> Hi Chris,
>
> Yes, this should be possible. The idea of using OSGi services and then
> distribute them without having to worry about the protocol is exactly
> what we had in mind when developing DOSGi!
> The CXF-DOSGi implementation currently supports: SOAP/HTTP and
> REST/HTTP. They can be configured by setting the org.apache.cxf.ws or
> org.apache.cxf.rs configuration type. If you don't specify a
> configuration type it defaults to org.apache.cxf.ws (SOAP).
>
> Currently these two are supported, there are people talking about
> supporting JMS as well, but it should be possible to add something
> completely different as well... For more information see:
> http://cxf.apache.org/distributed-osgi-reference.html
>
> Best regards,
>
> David
>
> On 25 February 2010 22:09, Clark, Chris <ch...@hp.com> wrote:
>> Hi there,
>>
>> I was just wondering, after struggling to incorporate CXF DOSGI into a long-running 'playground' project of mine, whether it is possible to use the DOSGI system provided with CXF for other front protocols - so can OSGi services be exposed via Hessian/Burlap/RMI/XML-RPC/etc... using this system.
>>
>> The whole idea that I had was that we had a load of OSGi services, but would like to be able to expose them dynamically, without any worry about the front-end protocol (whether it be SOAP/JSON/XML-RPC/Hessian/whatever).
>>
>> Does CXF DOSGI support this? and is there any documentation about it?
>>
>> Chris Clark
>>
>> "Audio, Video, Disco"
>