You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Puneet Gupta (JIRA)" <ji...@apache.org> on 2014/05/31 13:00:02 UTC

[jira] [Created] (CXF-5777) Axis2 client's array not compatible with Apache CXF Aegis Databinding

Puneet Gupta created CXF-5777:
---------------------------------

             Summary: Axis2 client's array not compatible with Apache CXF Aegis Databinding
                 Key: CXF-5777
                 URL: https://issues.apache.org/jira/browse/CXF-5777
             Project: CXF
          Issue Type: Test
          Components: Aegis Databinding
    Affects Versions: 2.7.11
         Environment: OS: Any
            Reporter: Puneet Gupta
            Priority: Blocker
             Fix For: 2.7.12


I am migrating service developed in Axis2 to Apache CXF. New service developed in apache cxf works but I am facing some problems to make it compatible with my older axis2 client.

I am trying to consume Apache CXF service with Aegis Data Binding through a Axis2 client. Aegis Data binding adds additional wrapper to arrays(ArrayOfCustomObject), if provided as a input parameter or required to be as output of service call. So there is difference in WSDL generated in case of Apache CXF and Axis2.

Problem Faced: If I am calling a service method which takes an array of custom class object as input parameter(lets say custom class have two properties), then at server side it creates two different custom class object(initializing properties to be null) even if the input array contains single custom class object.

What I think is that my service is not able to unmarshall the request in correct way. Is there any way through which we can configure service to except this array in correct way and additional wrapper i.e. ArrayOfCustomObject is not created in WSDL?

Any help solving this problem will be highly appreciated.

Regards, Puneet.



--
This message was sent by Atlassian JIRA
(v6.2#6252)