camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: Servlet and REST component integration is not complete
Date Mon, 21 Sep 2015 13:50:45 GMT
btw are the other questions about REST I may have missed?

Its great to hear that works on supporting it from CXF is in the works.

On Mon, Sep 21, 2015 at 3:43 PM, Claus Ibsen <claus.ibsen@gmail.com> wrote:
> Hi
>
> Yes there is no rest content negoation and whatnot in camel-core. That
> said if we find in the future a need for this we can surely add
> something. But the goal of the rest-dsl was to be that syntax sugar so
> ppl could do "route like" rest services, and then leave the bulk work
> to the existing rest capable Camel components.
>
> If we start adding rest logic in camel-core (or optional a camel-rest
> add-on module) then we may reinvent the wheel, or step on the toes of
> some of these components. But then on the other side if we have that
> logic then its consistent.
>
> The rest-dsl do have the json/xml binding included as those are the
> most common types to work with and they are generic and jackson and
> jaxb can work with those. And then more plain http components can do
> rest like services.
>
>
>
>
> On Mon, Sep 21, 2015 at 3:28 PM, Sergey Beryozkin <sberyozkin@gmail.com> wrote:
>> Hi Claus - thanks for getting back to this thread. That what I meant, that
>> after the camel-servlet based RESt-DSL consumer is up it does not enforce
>> Accept vs Produces intersection.
>>
>> Cheers, Sergey
>>
>> On 21/09/15 12:02, Claus Ibsen wrote:
>>>
>>> The rest-dsl is syntax sugar, and passes on the request to the actual
>>> transport, which then does what it care to do.
>>>
>>>
>>> On Tue, Aug 25, 2015 at 7:10 PM, Sergey Beryozkin <sberyozkin@gmail.com>
>>> wrote:
>>>>
>>>> Hi,
>>>> Experimenting a bit with a camel-example-servlet-rest-tomcat,
>>>> ServletComponent creates a Consumer for RESTComponent, and unless I'm
>>>> missing something, it ignores the consumes and produces initialization
>>>> properties - so
>>>>
>>>> curl -X GET -H "Accept: application/bar"
>>>> http://localhost:8080/camel-example-servlet-rest-tomcat/rest/user/123
>>>>
>>>> still returns JSON instead of HTTP error...
>>>> Don't mind creating a patch but perhaps someone who is more did this
>>>> integration can fix it given that I'm only starting looking at how REST
>>>> component is supported...
>>>>
>>>> Cheers, Sergey
>>>
>>>
>>>
>>>
>>
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2nd edition:
> https://www.manning.com/books/camel-in-action-second-edition



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2nd edition:
https://www.manning.com/books/camel-in-action-second-edition

Mime
View raw message