[
https://issues.apache.org/jira/browse/AXIS2-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186149#comment-13186149
]
Sagara Gunathunga commented on AXIS2-3761:
-------------------------------------------
Axis2 support for nested complex well. Can you test with one of the latest
release ? If you still face the same issue please reopen this issue and attach
your service class.
> Client Values not transmitting properly
> ---------------------------------------
>
> Key: AXIS2-3761
> URL: https://issues.apache.org/jira/browse/AXIS2-3761
> Project: Axis2
> Issue Type: Bug
> Components: rpc
> Affects Versions: 1.3
> Environment: Client is invoked from (witn in Eclipse) Windows XP and
> Server is Linux (RHEL 3)
> Reporter: Srinivasan Sairam
>
> My web services is using Axis 2.
> Some of the operations in the web services, take a complex object (obj1) as
> an input argument. This input object in turn contains another object (obj2).
>
> Signature looks something like:
> String operation1(Object1 obj1)
> Definition of Object1 :
> String name;
> Object obj2;
> Definition of Object2:
> String id = "";
> The client code is generated using xml binding. The client code has
> something like
> Obj1.obj2.setId("ID");
> Then the service is invoked, the operation1 receives empty string (which is
> the default value) for the id element.
> In the Soap Monitor, it shows that the server (entry point) is getting the
> value of "ID" for the objcet2's id element; but when it comes to the
> operation1 method, it is empty string.
> Has anyone seen such a behavior? Is there any workarounds?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
