[
https://issues.apache.org/jira/browse/CAMEL-7199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13910425#comment-13910425
]
Sergey Beryozkin edited comment on CAMEL-7199 at 2/24/14 3:58 PM:
------------------------------------------------------------------
Alexey, have a look please at a basic provider, CxfPayloadProvider. It's a
message body writer only.
I'm not attaching it as a patch but only as an example of how it can be easily
handled in cases where you have the existing code converting the data into
CxfPayload and expecting it be handled at the JAX-RS path.
Right now, this provider expects CxfPayload has a single JAXP Source part. This
can be easily enhanced for multiple sources be supported.
was (Author: sergey_beryozkin):
Alexey, have a look please at a basic provider, CxfPayloadProvider. It's a
message body writer only.
I'm not attaching it as a patch but only as an example of how it can be easily
handled in cases where you the existing code converting the data into
CxfPayload and expecting it be handled at the JAX-RS path.
Right now, this provider expects CxfPayload has a single JAXP Source part. This
can be easily enhanced for multiple sources be supported.
> [cxfrs] Consumer can't process CxfPayload from cxf producer
> -----------------------------------------------------------
>
> Key: CAMEL-7199
> URL: https://issues.apache.org/jira/browse/CAMEL-7199
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.12.2
> Reporter: Alexey Markevich
> Assignee: Willem Jiang
> Attachments: CxfPayloadProvider.java, camel-cxf-payload.zip
>
>
> I'm trying to migrate existing route from camel-jetty to camel-cxf.
> Route: from(cxfrs consumer).setBody().to(cxf producer)
> failed with "No message body writer has been found for response class
> CxfPayload"
> and convertBodyTo required.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
