camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William Tam (JIRA)" <>
Subject [jira] Commented: (CAMEL-1737) support Http central client API in camel-cxfrs producer
Date Wed, 05 Aug 2009 23:12:35 GMT


William Tam commented on CAMEL-1737:

Submitted revision 801457 for the following enhancements.

* The "WebClient-centric" camel-cxfrs producer can now propagate headers to/from camel exchange.
 It uses the standard header filtering mechanism so it can be customized.

* User can plug a custom CxfRsBinding implementation to affect the binding in the provider.

* By default, it drops the internal headers such as CamelCxfRsUsingHttpAPI (see the list in

* Only If the "CamelCxfRsResponseClass" header is NOT set (the default) or if it is set to, HTTP response headers and HTTP response code are propagated then
to Camel.  (It is a limitation in WebClient APIs).

* By default, the out message body is a object if CamelCxfRsResponseClass
is NOT set.  This gives users a bit more flexibility.  For example, the WebClient would throw
exception if response code is not equal to 200 when the response class is specified.  A converter
is created to convert from a Response to an InputStream.  Users can still get the old behavior
by setting the CamelCxfRsResponseClass header to InputStream class.

* Make sure setEndpointHeaderFilterStrategy() in called on non-spring configured CXF/CXF RS

* Remove component local header "CamelCxfRsMethod" and use the one defined in
(CamelHttpMethod) instead.

> support Http central client API in camel-cxfrs producer 
> --------------------------------------------------------
>                 Key: CAMEL-1737
>                 URL:
>             Project: Apache Camel
>          Issue Type: Sub-task
>            Reporter: Willem Jiang
>            Assignee: Willem Jiang
>             Fix For: 2.0-M3
> CXF  JAXRS endpoint provides a Http central client API , camel-cxfrs component should
leverage this API to give user more choice.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message