[
https://issues.apache.org/activemq/browse/CAMEL-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57431#action_57431
]
Christian Schneider commented on CAMEL-2396:
--------------------------------------------
Yes I will write a new Wiki documentation page.
About the tests I think we could need a integration test with CXF. I think one
test with CXF as client and one with CXF as server should help. The SOAPAction
header should then come from CXF through the JMS or HTTP component. For the
case where camel is the client I think we somehow have to add a SOAPAction
header while marshaling, as the Camel Proxy will not do it. Any idea how to do
this conceptionally?
> 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
>
>
> 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.
