[
https://issues.apache.org/activemq/browse/CAMEL-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-536 started by Willem Jiang.
> camel-cxf component not propagating context data
> ------------------------------------------------
>
> Key: CAMEL-536
> URL: https://issues.apache.org/activemq/browse/CAMEL-536
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 1.3.0
> Reporter: Eamonn Dwyer
> Assignee: Willem Jiang
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> For POJO data formats the CxfProducer currently invokes the following method
> to invoke on a target server
> result = client.invoke(operation, parameters.toArray());
> This fails to setup the Request and Response contexts for the out (request)
> message and in (response) message. It should instead be copying the relevant
> data from the consumer and invoking the following operation on the Client
> interface
> Object[] invoke(BindingOperationInfo oi, Object[] params, Map<String,
> Object> context) throws Exception;
> Likewise the PAYLOAD and MESSAGE data formats are not setting up their
> contexts before they call the dispatch operation. In fact there is comments
> in the current codebase...
> // invoke the message prepare the context
> Map<String, Object> context = new HashMap<String, Object>();
> Map<String, Object> requestContext = new HashMap<String,
> Object>();
> Map<String, Object> responseContext = new HashMap<String,
> Object>();
> // TODO Get the requestContext from the CamelExchange
> context.put(CxfClient.REQUEST_CONTEXT, requestContext);
> context.put(CxfClient.RESPONSE_CONTEXT, responseContext);
> The fix should also include a fix for all three data format types
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
