axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amila Chinthaka Suriarachchi (JIRA)" <>
Subject [jira] Resolved: (AXIS2-2590) ASP.NET Interop and other issues.
Date Thu, 26 Apr 2007 05:34:15 GMT


Amila Chinthaka Suriarachchi resolved AXIS2-2590.

    Resolution: Fixed

I invoked and see the UpdateBalance method it works fine. 
1. when using enumeration classes one have to use the constant enumerations defined.


3. you have to use the 
<parameter name="useOriginalwsdl" locked="false">true</parameter> in server.xml
Now (in axis2 1.2) wsdl2java put this parameter to services.xml as well

This is a document/literal wsdl. So changing the part name should not make any effect to the
soap message passed. So that change should not make any interoperatebility issue.

> ASP.NET Interop and other issues.
> ---------------------------------
>                 Key: AXIS2-2590
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>            Reporter: Davanum Srinivas
>         Assigned To: Amila Chinthaka Suriarachchi
> Schema and WSDL are here -
> 1)       If we call UpdateBalanceInput on the raw Java produced by WSDL2JAVA, it gets
an instantiation exception because it doesn't create a zero-argument instantiator for the
enumeration type BalanceOperationType.  I have to manually add it and make the protected one-arg
version public for it to work.
> 2)       Even then, the operation that gets passed in is null in all cases.  In fact,
all wrapped objects are passed in as null.  Wrapped objects that they return come back to
the client fine.
> 3)       If I ask for the wsdl by doing DataService?wsdl, all the 'part name="parameters"'
lines turn into '<part name="part0"', which breaks ASP.NET when it tries to connect.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message