[ https://issues.apache.org/jira/browse/CAMEL-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raul Kripalani updated CAMEL-5916: ---------------------------------- Fix Version/s: (was: 2.11.1) 2.11.0 Summary: CXFRS: Simpler, higher-level binding style injecting headers, attachments and entity (was: CXFRS: Simpler, higher-level binding style injecting headers, attachements and entity) > CXFRS: Simpler, higher-level binding style injecting headers, attachments and > entity > ------------------------------------------------------------------------------------ > > Key: CAMEL-5916 > URL: https://issues.apache.org/jira/browse/CAMEL-5916 > Project: Camel > Issue Type: New Feature > Components: camel-cxf > Reporter: Raul Kripalani > Assignee: Raul Kripalani > Fix For: 2.11.0 > > > The camel-cxfrs consumer currently dumps the {{MessageContentList}} coming > from the CXF stack into the Message body. The route then has to do much > lower-level processing than usual, and is tightly coupled with the method > signature of the JAX-RS operation. > We should offer a CxfRsBinding that is more user-friendly and makes the > request data more accesible to the route. Aim for the following: > - Map JAX-RS parameters (@HeaderParam, @QueryParam, etc.) as Camel IN message > headers. > - Set the request entity as the IN message body. > - Inject binary @Multipart attachments as Camel IN message attachments. > Additionally, path parameters along the Subresource locator chain should be > mapped as headers too. See > http://camel.465427.n5.nabble.com/camel-cxfrs-Handling-of-Subresources-td5724615.html > for context. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira