[
https://issues.apache.org/activemq/browse/CAMEL-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57481#action_57481
]
Willem Jiang commented on CAMEL-2396:
-------------------------------------
@Christian
I think the soap action should be put into the message, as it is per message.
We need to map the soap action from the jms properties and http headers to
camel message header, just like mapping a protocol header into a camel common
header. In this way the camel user will not be bothered by the issue of Tibco
BW SoapAction.
And camel-cxf also need to do the same thing.
Thoughts ?
> Add a DataFormat for handling JAXB data inside SOAP
> ---------------------------------------------------
>
> Key: CAMEL-2396
> URL: https://issues.apache.org/activemq/browse/CAMEL-2396
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-jaxb
> Reporter: Christian Schneider
> Assignee: Willem Jiang
> Fix For: 2.3.0
>
> Attachments: camel-soap-2010-02-07.patch,
> camel-soap-2010-02-08.patch, camel-soap-no-classresolver-2010-02-09.patch
>
>
> Currently a user who wants to implement or call webservices needs to use one
> of the heavy weight frameworks (CXF or Axis) even for simple cases.
> So we should have a SoapJaxbDataFormat that simply allows to add or remove
> the Soap Envelope and Body around one data element that is then processed
> using JAXB. The Data format should only handle the case of doc/lit services.
> The stub code can be generated using the cxf WSDL2Java or Codegen maven
> plugin but there should be no runtime dependency on CXF or Axis.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
