There was an issue reported on the user's mailing list in March 2002 regarding Axis RPC responses that contain complex types. Axis was prefixing the elements within the complex type with a namespace prefix. This caused .net clients to fail to correctly parse the response message. There are no errors, but the response object is empty (all values null). The mailing list thread is here: http://marc.theaimsgroup.com/?l=axis-user&m=101793858607643&w=2. Apparently in the 4/3/2002 build this was fixed, Axis no longer sent the prefixes on complexType elements. However, in the current 1.1 release build, Axis is prefixing complexType elements.
I've searched the mailing list for complaints about this and have found none. I also cannot find a bug logged for this issue, either fixed or open. I assume that I am doing something incorrectly in my client, no one is using .net clients for axis services, or there is a configuration issue with my Axis server. Can anyone shed any light on what the deal is here? We are currently unable to invoke any Axis hosted web service that returns a complex type with a .net client. Thanks.
