camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <>
Subject [jira] Commented: (CAMEL-2396) Add a DataFormat for handling JAXB data inside SOAP
Date Tue, 09 Feb 2010 21:05:34 GMT


Christian Schneider commented on CAMEL-2396:

Hi Willem,

I currently try to include the soap action into the CamelInvocationHandler. I am not sure
if the soap action should go into the message as a header or into the exchange as a property.
Where do you think it should go?

As the constant is named CamelSoapAction it will not make sense in the jms properties or the
http headers anyway. So we need to convert it there into a HTTP header named SOAPAction or
a jms property named SOAPAction (or in the case of Tibco BW SoapAction). I first thought it
is inconvenient that the endpoint has to convert here but I now think it is good to abstract
this a little. Btw. we should also make camel-cxf consistent to how we handle the soap action
by setting respectively evaluating the CamelSoapAction. 

> Add a DataFormat for handling JAXB data inside SOAP
> ---------------------------------------------------
>                 Key: CAMEL-2396
>                 URL:
>             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.

View raw message