camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antoine DESSAIGNE <antoine.dessai...@gmail.com>
Subject Re: Feature request: support setOutBody in XML definitions
Date Fri, 07 Jun 2013 12:29:01 GMT
I wasn't able to find the issue you're mentioning in Jira, by any change do
you have the issue number ?

Thanks a lot,

Antoine.


2013/6/7 Claus Ibsen <claus.ibsen@gmail.com>

> Because <setBody> handles this internally as well the Camel routing engine.
>
> And there was a bug in Camel, so when you had short routes, like
>
> from X
>  setBody
>
> This is fixed in recent/upcoming releases (cant remember exact when)
>
> Also see this FAQ
> http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html
>
> On Fri, Jun 7, 2013 at 9:32 AM, Antoine DESSAIGNE
> <antoine.dessaigne@gmail.com> wrote:
> > Hi,
> >
> > Why are they deprecated ?
> >
> > I want to create a restlet consumer (see [1]) using XML, and the
> > documentation states that the response should be defined in the OUT
> message.
> >
> > As of today I was the following sample code
> >     <!-- Route used to make a restlet server -->
> >     <route>
> >         <from uri="restlet:http://localhost:8888/hello/{id}"/>
> >         <setBody>
> >             <simple>Hello ${headers[id]} !</simple>
> >         </setBody>
> >         <to uri="mock:mock" />
> >     </route>
> >
> > How can I set the response in the OUT message ?
> >
> > Also, I there a way to avoid needing <to uri="mock:mock" /> ?
> >
> > Thanks a lot for your help,
> >
> > Antoine.
> >
> > [1] http://camel.apache.org/restlet.html#Restlet-MessageBody
> >
> >
> > 2013/6/6 Claus Ibsen <claus.ibsen@gmail.com>
> >
> >> Hi
> >>
> >> Yeah all the setOut is @deprecated as you should just use setBody /
> >> setHeader etc.
> >> So this is on purpose why there is no <setOutBody> in the XML DSL
> >>
> >> On Thu, Jun 6, 2013 at 5:52 PM, Antoine DESSAIGNE
> >> <antoine.dessaigne@gmail.com> wrote:
> >> > Hi everyone,
> >> >
> >> > I didn't found the <setOutBody> XML tag and I was wondering whether
> there
> >> > was a reason for that ?
> >> >
> >> > Otherwise, I will submit a patch for fixing this gap.
> >> >
> >> > Thanks a lot,
> >> >
> >> > Antoine.
> >>
> >>
> >>
> >> --
> >> Claus Ibsen
> >> -----------------
> >> www.camelone.org: The open source integration conference.
> >>
> >> Red Hat, Inc.
> >> FuseSource is now part of Red Hat
> >> Email: cibsen@redhat.com
> >> Web: http://fusesource.com
> >> Twitter: davsclaus
> >> Blog: http://davsclaus.com
> >> Author of Camel in Action: http://www.manning.com/ibsen
> >>
>
>
>
> --
> Claus Ibsen
> -----------------
> www.camelone.org: The open source integration conference.
>
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: cibsen@redhat.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message