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 Wed, 27 Jan 2010 07:54:34 GMT


Christian Schneider commented on CAMEL-2396:

Hi Willem,

1. If you prefer I can create a new module and update the patch. As the SoapJaxbDataformat
is based on Jaxb and does not add new dependencies I think we could also leave it in camel-jaxb.

2. I just replaced the this.getClass.forName() with the ClassResolver. Th problem is that
I now get ClassNotFoundExceptions. Is there anything else I have to do to make it work?

3. I did not completely understand this. Do you mean I should add a constant in the Exchange

About the ServiceInterfaceStrategy:
In case of a wrapped definition I look at the RequestWrapper or ResponseWrapper annotations.
In case these Annotations are not present I use the WebParam annotation of the parameter of
the method or the WebResult annotation of the return type.
The isClient property will be used to determine if the request or response is to be analyzed.
This strategy does not yet work though.

I also have a question that perhaps you can answer. I create code for the CustomerService.wsdl.
Currently this will always create wrapped style code. Is there a setting for codegen to create
bare style? So my methods look like:
GetCustomerResponse getCustomersByName(GetCustomer request);

> 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.2.0
>         Attachments: camel-jaxb-2010-01-26.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