You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by "Kasim Sert (Ibtech-Software Infrastructure)" <ka...@ibtech.com.tr> on 2016/08/31 07:00:52 UTC
CXFRS vs New Rest DSL
Hi,
As company we have many soap and rest services and we want to rewrite our framework and move these services to camel-cxf.
I like the idea of having one interface definition and being able to expose it as soap and rest at the same time, I think we can do this with cxfrs.
However as far as I see camel community promotes new rest dsl which do not support cxf-rs currently.also swagger support also seem to be a question mark in cxfrs case.
Can somebody list pros and cons of these two frameworks, which one to choose in which condition especially if it will be used heavily.
[Facebook]<http://www.facebook.com/Finansbank> [Twitter] <http://twitter.com/finansbank>
[https://www.finansbank.com.tr/Disclaimer/BannerImages.aspx?date=31.08.201610:0000]<https://www.finansbank.com.tr/Disclaimer/Bannerlink.aspx?date=31.08.201610:0000>
Bu e-posta'n?n i?erdi?i bilgiler (ekleri dahil olmak ?zere) gizlidir. Onay?m?z olmaks?z?n ???nc? ki?ilere a?iklanamaz. Bu mesaj?n g?nderilmek istendi?i ki?i de?ilseniz, l?tfen mesaj? sisteminizden derhal siliniz. IBTech A.?. bu mesaj?n i?erdi?i bilgilerin do?rulu?u veya eksiksiz oldu?u konusunda bir garanti vermemektedir. Bu nedenle bilgilerin ne ?ekilde olursa olsun i?eri?inden, iletilmesinden, al?nmas?ndan, saklanmas?ndan sorumlu de?ildir. Bu mesaj?n i?eri?i yazar?na ait olup, IBTech A.?.'nin g?r??lerini i?ermeyebilir.
The information contained in this e-mail (including any attachments)is confidential. It must not be disclosed to any person without our authority. If you are not the intended recipient, please delete it from your system immediately. IBTech A.S. makes no warranty as to the accuracy or completeness of any information contained in this message and hereby excludes any liability of any kind for the information contained therein or for the information transmission, reception, storage or use of such in any way whatsoever. Any opinions expressed in this message are those of the author and may not necessarily reflect the opinions of IBTech A.S.
Re: CXFRS vs New Rest DSL
Posted by Brad Johnson <br...@mediadriver.com>.
Personally I prefer CXF and generally expose Rest and SOAP via annotations
on the same interface. I then use a RecipientList to route the
operationName of the method invoked to the same place. That way I get both
SOAP and Rest without any extra work.
But let me temper that statement by saying that I haven't used the Rest DSL
that much. One thing I will say is I was very disappointed in the design
decision to embed the Rest DSL in the RouteBuilder. It should be its own
class or extension of RouteBuilder whether it lives in the same bundle/jar
or in a different one.
Brad
On Wed, Aug 31, 2016 at 9:55 AM, Matt Sicker <bo...@gmail.com> wrote:
> I like using the REST DSL over CXF because there's a lot less boilerplate,
> and I don't need to expose a SOAP service or anything overly complicated
> that CXF supports. For simple REST API use cases, the REST DSL is great
> when your API makes heavy use of Camel routes.
>
> On 31 August 2016 at 04:01, Sergey Beryozkin <sb...@gmail.com> wrote:
>
> > Unfortunately I haven't finished yet my project for converting CXFRS to
> > work with REST DSL (I'm committed to it but finding it very hard to find
> > the time to get it finished - the initial code is already available but
> > requires a good bit of polishing).
> >
> > REST DSL works on top of different implementations. Pros are is that you
> > get a route DSL not tied to a specific HTTP-aware component. I won't go
> > into possible cons but might do when I get CXFRS supporting REST DSL :-)
> >
> > Sergey
> >
> > On 31/08/16 08:00, Kasim Sert (Ibtech-Software Infrastructure) wrote:
> >
> >> Hi,
> >>
> >> As company we have many soap and rest services and we want to rewrite
> our
> >> framework and move these services to camel-cxf.
> >> I like the idea of having one interface definition and being able to
> >> expose it as soap and rest at the same time, I think we can do this with
> >> cxfrs.
> >> However as far as I see camel community promotes new rest dsl which do
> >> not support cxf-rs currently.also swagger support also seem to be a
> >> question mark in cxfrs case.
> >> Can somebody list pros and cons of these two frameworks, which one to
> >> choose in which condition especially if it will be used heavily.
> >>
> >>
> >>
> >> [Facebook]<http://www.facebook.com/Finansbank> [Twitter] <
> >> http://twitter.com/finansbank>
> >>
> >> [https://www.finansbank.com.tr/Disclaimer/BannerImages.aspx?
> >> date=31.08.201610:0000]<https://www.finansbank.com.tr/Discla
> >> imer/Bannerlink.aspx?date=31.08.201610:0000>
> >>
> >>
> >> Bu e-posta'n?n i?erdi?i bilgiler (ekleri dahil olmak ?zere) gizlidir.
> >> Onay?m?z olmaks?z?n ???nc? ki?ilere a?iklanamaz. Bu mesaj?n g?nderilmek
> >> istendi?i ki?i de?ilseniz, l?tfen mesaj? sisteminizden derhal siliniz.
> >> IBTech A.?. bu mesaj?n i?erdi?i bilgilerin do?rulu?u veya eksiksiz
> oldu?u
> >> konusunda bir garanti vermemektedir. Bu nedenle bilgilerin ne ?ekilde
> >> olursa olsun i?eri?inden, iletilmesinden, al?nmas?ndan, saklanmas?ndan
> >> sorumlu de?ildir. Bu mesaj?n i?eri?i yazar?na ait olup, IBTech A.?.'nin
> >> g?r??lerini i?ermeyebilir.
> >>
> >> The information contained in this e-mail (including any attachments)is
> >> confidential. It must not be disclosed to any person without our
> authority.
> >> If you are not the intended recipient, please delete it from your system
> >> immediately. IBTech A.S. makes no warranty as to the accuracy or
> >> completeness of any information contained in this message and hereby
> >> excludes any liability of any kind for the information contained
> therein or
> >> for the information transmission, reception, storage or use of such in
> any
> >> way whatsoever. Any opinions expressed in this message are those of the
> >> author and may not necessarily reflect the opinions of IBTech A.S.
> >>
> >>
> >
> > --
> > Sergey Beryozkin
> >
> > Talend Community Coders
> > http://coders.talend.com/
> >
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
>
Re: CXFRS vs New Rest DSL
Posted by Matt Sicker <bo...@gmail.com>.
I like using the REST DSL over CXF because there's a lot less boilerplate,
and I don't need to expose a SOAP service or anything overly complicated
that CXF supports. For simple REST API use cases, the REST DSL is great
when your API makes heavy use of Camel routes.
On 31 August 2016 at 04:01, Sergey Beryozkin <sb...@gmail.com> wrote:
> Unfortunately I haven't finished yet my project for converting CXFRS to
> work with REST DSL (I'm committed to it but finding it very hard to find
> the time to get it finished - the initial code is already available but
> requires a good bit of polishing).
>
> REST DSL works on top of different implementations. Pros are is that you
> get a route DSL not tied to a specific HTTP-aware component. I won't go
> into possible cons but might do when I get CXFRS supporting REST DSL :-)
>
> Sergey
>
> On 31/08/16 08:00, Kasim Sert (Ibtech-Software Infrastructure) wrote:
>
>> Hi,
>>
>> As company we have many soap and rest services and we want to rewrite our
>> framework and move these services to camel-cxf.
>> I like the idea of having one interface definition and being able to
>> expose it as soap and rest at the same time, I think we can do this with
>> cxfrs.
>> However as far as I see camel community promotes new rest dsl which do
>> not support cxf-rs currently.also swagger support also seem to be a
>> question mark in cxfrs case.
>> Can somebody list pros and cons of these two frameworks, which one to
>> choose in which condition especially if it will be used heavily.
>>
>>
>>
>> [Facebook]<http://www.facebook.com/Finansbank> [Twitter] <
>> http://twitter.com/finansbank>
>>
>> [https://www.finansbank.com.tr/Disclaimer/BannerImages.aspx?
>> date=31.08.201610:0000]<https://www.finansbank.com.tr/Discla
>> imer/Bannerlink.aspx?date=31.08.201610:0000>
>>
>>
>> Bu e-posta'n?n i?erdi?i bilgiler (ekleri dahil olmak ?zere) gizlidir.
>> Onay?m?z olmaks?z?n ???nc? ki?ilere a?iklanamaz. Bu mesaj?n g?nderilmek
>> istendi?i ki?i de?ilseniz, l?tfen mesaj? sisteminizden derhal siliniz.
>> IBTech A.?. bu mesaj?n i?erdi?i bilgilerin do?rulu?u veya eksiksiz oldu?u
>> konusunda bir garanti vermemektedir. Bu nedenle bilgilerin ne ?ekilde
>> olursa olsun i?eri?inden, iletilmesinden, al?nmas?ndan, saklanmas?ndan
>> sorumlu de?ildir. Bu mesaj?n i?eri?i yazar?na ait olup, IBTech A.?.'nin
>> g?r??lerini i?ermeyebilir.
>>
>> The information contained in this e-mail (including any attachments)is
>> confidential. It must not be disclosed to any person without our authority.
>> If you are not the intended recipient, please delete it from your system
>> immediately. IBTech A.S. makes no warranty as to the accuracy or
>> completeness of any information contained in this message and hereby
>> excludes any liability of any kind for the information contained therein or
>> for the information transmission, reception, storage or use of such in any
>> way whatsoever. Any opinions expressed in this message are those of the
>> author and may not necessarily reflect the opinions of IBTech A.S.
>>
>>
>
> --
> Sergey Beryozkin
>
> Talend Community Coders
> http://coders.talend.com/
>
--
Matt Sicker <bo...@gmail.com>
Re: CXFRS vs New Rest DSL
Posted by Sergey Beryozkin <sb...@gmail.com>.
Unfortunately I haven't finished yet my project for converting CXFRS to
work with REST DSL (I'm committed to it but finding it very hard to find
the time to get it finished - the initial code is already available but
requires a good bit of polishing).
REST DSL works on top of different implementations. Pros are is that you
get a route DSL not tied to a specific HTTP-aware component. I won't go
into possible cons but might do when I get CXFRS supporting REST DSL :-)
Sergey
On 31/08/16 08:00, Kasim Sert (Ibtech-Software Infrastructure) wrote:
> Hi,
>
> As company we have many soap and rest services and we want to rewrite our framework and move these services to camel-cxf.
> I like the idea of having one interface definition and being able to expose it as soap and rest at the same time, I think we can do this with cxfrs.
> However as far as I see camel community promotes new rest dsl which do not support cxf-rs currently.also swagger support also seem to be a question mark in cxfrs case.
> Can somebody list pros and cons of these two frameworks, which one to choose in which condition especially if it will be used heavily.
>
>
>
> [Facebook]<http://www.facebook.com/Finansbank> [Twitter] <http://twitter.com/finansbank>
>
> [https://www.finansbank.com.tr/Disclaimer/BannerImages.aspx?date=31.08.201610:0000]<https://www.finansbank.com.tr/Disclaimer/Bannerlink.aspx?date=31.08.201610:0000>
>
>
> Bu e-posta'n?n i?erdi?i bilgiler (ekleri dahil olmak ?zere) gizlidir. Onay?m?z olmaks?z?n ???nc? ki?ilere a?iklanamaz. Bu mesaj?n g?nderilmek istendi?i ki?i de?ilseniz, l?tfen mesaj? sisteminizden derhal siliniz. IBTech A.?. bu mesaj?n i?erdi?i bilgilerin do?rulu?u veya eksiksiz oldu?u konusunda bir garanti vermemektedir. Bu nedenle bilgilerin ne ?ekilde olursa olsun i?eri?inden, iletilmesinden, al?nmas?ndan, saklanmas?ndan sorumlu de?ildir. Bu mesaj?n i?eri?i yazar?na ait olup, IBTech A.?.'nin g?r??lerini i?ermeyebilir.
>
> The information contained in this e-mail (including any attachments)is confidential. It must not be disclosed to any person without our authority. If you are not the intended recipient, please delete it from your system immediately. IBTech A.S. makes no warranty as to the accuracy or completeness of any information contained in this message and hereby excludes any liability of any kind for the information contained therein or for the information transmission, reception, storage or use of such in any way whatsoever. Any opinions expressed in this message are those of the author and may not necessarily reflect the opinions of IBTech A.S.
>
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/