Hi guys,

Take a look at the new Simple binding style for CXFRS consumers, which
greatly simplifies consuming REST requests:
https://cwiki.apache.org/confluence/display/CAMEL/CXFRS#CXFRS-ConsumingaRESTRequestSimpleBindingStyle
.

Fresh out of the oven.

Regards,

*Raúl Kripalani*
Enterprise Architect, Open Source Integration specialist, Program
Manager | Apache
Camel Committer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk

On Fri, Mar 29, 2013 at 6:43 PM, Chris Wolf <cwolf.a...@gmail.com> wrote:

> Hello - I just used camel-http to do my RESTful service invocation and
> it's good enough for my basic purposes.
>
>    -Chris
>
> On Fri, Mar 29, 2013 at 11:30 AM, Chris Wolf <cwolf.a...@gmail.com> wrote:
> > On Fri, Mar 29, 2013 at 9:23 AM, Sergey Beryozkin <sberyoz...@gmail.com>
> wrote:
> >> On 29/03/13 11:05, Claus Ibsen wrote:
> >>>
> >>> Hi
> >>>
> >>> There is also camel-restlet
> >>> http://camel.apache.org/restlet
> >>>
> >>> It may be easier to get hold of and use. But CXF may have more
> >>> configuration options, but is also IMHO harder to get started with
> >>> using - some of that is us to blame, for not having better
> >>> documentation and samples. And the fact that IMHO camel-cxf has both
> >>> WS and RS in the same big giant component, which IMHO is becoming a
> >>> problem and hurts the lightweightness of Camel and CXF.
> >>
> >> Really ? I agree that it is not the easiest component to use - that is
> fare
> >> and personally I'd have no problems with sharing part of the 'blame'
> for not
> >> contributing, but please don't do this "hurts the Camel " thing, which
> is
> >> FUD IMHO - FYI, I'm perfectly fine with yourself having the
> preferences, no
> >> problems there at all !
> >>
> >> Chris: feel free to experiment with all the other HTTP-aware components,
> >> some of them indeed are simpler to use for a given task.
> >> FYI, I'm going to work on doing a better demo of using CXF JAX-RS
> endpoints
> >> directly within Camel, specifically, using the Camel transport to link
> >> directly to CXF jaxrs:endpoints, and will update the list.
> >>
> >> Thanks, Sergey
> >
> > Even just a basic client making an HTTP GET and getting back some text
> > would be great. I still can't do that.
> > (See my recent reply to Claus)
> >
> > Thanks,
> >
> > Chris
> >
> >>>
> >>>
> >>> You may also take a look at some of the articles about Camel. There
> >>> should be some good ones about REST etc
> >>> http://camel.apache.org/articles
> >>>
> >>> For example this article
> >>> http://www.ofbizian.com/2012/02/apache-camel-rest-example.html
> >>>
> >>> But there is others as well.
> >>>
> >>>
> >>>
> >>> On Thu, Mar 28, 2013 at 11:35 PM, Chris Wolf<cwolf.a...@gmail.com>
>  wrote:
> >>>>
> >>>> So I have the book, "Camel In Action", which is a very good and
> >>>> thorough treatment of camel-core. However, now my development efforts
> >>>> are starting to hit severe turbulence upon making the jump from
> >>>> camel-core to camel-cxf, in particular, how to consume a RESTful
> >>>> service?
> >>>>
> >>>> I read these:
> >>>> http://camel.apache.org/cxfrs.html
> >>>> http://camel.apache.org/cxf-bean-component.html
> >>>>
> >>>> ...but these pages seem to be reference pages for people who have
> >>>> already mastered camel-cxfrs - not newbies, like me.  Can anyone point
> >>>> me to an end-to-end example?  I don't need the server-side - this is
> >>>> legacy and produces XML.
> >>>>
> >>>> N.B. Outside of Camel, I have had much previous experience using CXF
> >>>> for JAX-WS style services, client and server  (never JAX-RS, though)
> >>>>
> >>>> Thanks for any help,
> >>>>
> >>>>    -Chris
> >>>
> >>>
> >>>
> >>>
> >>
> >>
>

Reply via email to