On 5/3/06, Rich Rodriguez <[EMAIL PROTECTED]> wrote:
With the Axis 1.3 BeanSerializer the array "items" seem to be named the same as the array property itself. This is fixed in the next version?On 5/3/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:Edit the WSDL and change the elements named "item" in your two arrays to unique names. You need to be using Axis 1.4 to get it to generate the appropriate SOAP messages, though.On 5/3/06, Santunu Podder <[EMAIL PROTECTED]> wrote:Hi All,
I am having a problem invoking a java web service from a .Net 1.1 client.
The apache axis generated wsdl specifies a class member of type array
which incidently results in exception while invocation. The error I am
getting is as below :
Unhandled Exception: System.InvalidOperationException: Method
TestServices.createAccount can not be reflected.
---> System.InvalidOperationException: There was an error
reflecting 'createAccountResult'.
---> System.InvalidOperationException: There was an error
reflecting type 'test.services.AccountTransactionResponse'.
---> System.InvalidOperationException : There was an error
reflecting field 'amounts'.
---> System.InvalidOperationException: The XML element named
'item' from namespace ' http://localhost:8080/axis/services/Account '
references distinct types test.services.AccountDetails and
System.Double.
Use XML attributes to specify another XML name or
namespace for the element or types.
The member amounts is of type array and looks like the error is because of
that.
But .Net 2.0 client does not have this problem. A java client does not
have any problem either.
Could anybody please let me know how to overcome this.
Thanks in advance,
Santunu
This message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorised use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. Close Premium Finance shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Close Premium Finance does not guarantee that the integrity of this communication has been maintained nor that this communication is free of viruses, interceptions or interference.
