DO NOT REPLY [Bug 20683] New: - Interop problem with Microsoft .NET 1.1 and sendMultiRef parameter

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20683>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20683

Interop problem with Microsoft .NET 1.1 and sendMultiRef parameter

           Summary: Interop problem with Microsoft .NET 1.1 and sendMultiRef
                    parameter
           Product: Axis
           Version: current (nightly)
          Platform: All
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Basic Architecture
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: rkellogg@micros.com


Attached you will find a very simple web service that returns a JavaBean to a 
Microsoft .NET Framework 1.1 client.

The WSDD file follows:
 <deployment name="EMSService-Deployment"
             xmlns="http://xml.apache.org/axis/wsdd/"
             xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"
             xmlns:xsd="http://www.w3.org/2000/10/XMLSchema"
             xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance">
  <service name="EMSService" provider="java:RPC" xmlns:emsdatans="urn:micros-
webservices:emsdata">
    <namespace>urn:micros-webservices:ems</namespace>
    <parameter name="className" value="com.micros.portal.ems.EMSService" />
    <parameter name="allowedMethods" value="Login" />
    <parameter name="sendMultiRefs" value="false"/>
    <beanMapping qname="emsdatans:UserInfoTO" 
languageSpecificType="java:com.micros.portal.ems.objects.UserInfoTO" />
  </service>
</deployment>

Please notice the use of the sendMultiRefs parameter.  With this parameter 
specified, the Axis 1.1 June 9, 2003 release returns the following HTTP 
response:

<?xml version="1.0" encoding="UTF-8"?>
   <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> 
      <soapenv:Body>  
         <ns1:LoginResponse 
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" 
xmlns:ns1="urn:micros-webservices:ems">   
            <ns1:LoginReturn xsi:type="ns2:UserInfoTO" xmlns:ns2="urn:micros-
webservices:emsdata">    
               <ns1:displayName xsi:type="xsd:string">Demo 
User</ns1:displayName>    
               <ns1:languageCountry xsi:type="xsd:string">de-
DE</ns1:languageCountry>    
               <ns1:orgLevelId xsi:type="xsd:long">19551</ns1:orgLevelId>    
               <ns1:organizationId 
xsi:type="xsd:long">1000</ns1:organizationId>    
               <ns1:organizationName 
xsi:type="xsd:string">HMS</ns1:organizationName>    
               <ns1:roleName xsi:type="xsd:string">Sys Admin</ns1:roleName>    
               <ns1:userId xsi:type="xsd:long">18060</ns1:userId>   
            </ns1:LoginReturn>  
         </ns1:LoginResponse> 
      </soapenv:Body>
   </soapenv:Envelope>   

Under the Axis 1.1 April 16, 2003 release, the response was as follows:
<?xml version="1.0" encoding="UTF-8"?>
   <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> 
      <soapenv:Body>  
         <ns1:LoginResponse 
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" 
xmlns:ns1="urn:micros-webservices:ems">   
            <LoginReturn xsi:type="ns2:UserInfoTO" xmlns:ns2="urn:micros-
webservices:emsdata">    
               <displayName xsi:type="xsd:string">Demo User</displayName>    
               <languageCountry xsi:type="xsd:string">de-
DE</languageCountry>    
               <orgLevelId xsi:type="xsd:long">19551</orgLevelId>    
               <organizationId xsi:type="xsd:long">1000</organizationId>    
               <organizationName 
xsi:type="xsd:string">HMS</organizationName>    
               <roleName xsi:type="xsd:string">Sys Admin</roleName>    
               <userId xsi:type="xsd:long">18060</userId>   
            </LoginReturn>  
         </ns1:LoginResponse> 
      </soapenv:Body>
   </soapenv:Envelope>

You will notice the ns1: prefix added to each of the LoginResponse elements.  

The April 16, 2003 release can be properly deserialized by the .NET Framework 
while the June 9, 2003 release fails silently.

Environment:
JBOSS 3.2.0
JDK 1.4.1_02
Microsoft Windows 2000 SP3 
Microsoft VS.NET 2003 (with .NET Framework 1.1)

Source and WSDD file have been attached.  Thanks.