Return-Path: 
 <axis-user-return-34387-apmail-ws-axis-user-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-user-archive@www.apache.org
Received: (qmail 82968 invoked from network); 23 Jun 2005 09:08:14 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 23 Jun 2005 09:08:14 -0000
Received: (qmail 91038 invoked by uid 500); 23 Jun 2005 09:08:04 -0000
Delivered-To: apmail-ws-axis-user-archive@ws.apache.org
Received: (qmail 91021 invoked by uid 500); 23 Jun 2005 09:08:03 -0000
Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
list-help: <mailto:axis-user-help@ws.apache.org>
list-unsubscribe: <mailto:axis-user-unsubscribe@ws.apache.org>
List-Post: <mailto:axis-user@ws.apache.org>
List-Id: <axis-user.ws.apache.org>
Delivered-To: mailing list axis-user@ws.apache.org
Received: (qmail 91008 invoked by uid 99); 23 Jun 2005 09:08:03 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Jun 2005 02:08:03 -0700
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of Duarte.Moreira@altitude.com
 designates 193.126.30.202 as permitted sender)
Received: from [193.126.30.202] (HELO mx1.altitude.com) (193.126.30.202)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Jun 2005 02:08:03 -0700
Received: from EXCH01.ascorp.net ([10.254.0.101] RDNS failed) by
 mx1.altitude.com with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 23 Jun 2005 10:06:55 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Bug with Arrays as Return Types
Date: Thu, 23 Jun 2005 10:12:48 +0100
Message-ID: <B51EE03D1BD53F4F9053962B485654E701711ED0@EXCH01.ascorp.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Bug with Arrays as Return Types
thread-index: AcV3bsaO2GrUxLtlRZq1wJLzGyIGxQAZMoNw
From: "Duarte Marques Moreira" <Duarte.Moreira@altitude.com>
To: <axis-user@ws.apache.org>
X-OriginalArrivalTime: 23 Jun 2005 09:06:55.0646 (UTC)
 FILETIME=[E73F73E0:01C577D2]
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Hello,


With Axis 1.1 you have:

   ... xsi:type=3D"soapenc:Array" soapenc:arrayType=3D"xsd:string[3]" =
...

With Axis 1.2 you have:

   ... soapenc:arrayType=3D"soapenc:string[3]" =
xsi:type=3D"soapenc:Array"=20

I have updated the ArraySerializer.java in order to change the order of
the attributes (xsi:type=3D"soapenc:Array" must come first) and it seems
to work with .Net

Duarte


-----Original Message-----
From: Andrew Vardeman [mailto:andrewv@iastate.edu]=20
Sent: quarta-feira, 22 de Junho de 2005 21:59
To: axis-user@ws.apache.org
Subject: Re: Bug with Arrays as Return Types

I've put together two webapps for comparision: one using Axis 1.1, the=20
other using Axis 1.2.  They can be downloaded here:

http://www.public.iastate.edu/~andrewv/axis/webapps.zip

They each have one service, StringArrayServer.  In each case, the
service=20
is implemented by a Java class with one method:

String[] getStringArray();

Each service is deployed via the AdminClient with the following
deploy.wsdd:

<deployment name=3D"test" xmlns=3D"http://xml.apache.org/axis/wsdd/"
xmlns:java=3D"http://xml.apache.org/axis/wsdd/providers/java"
xmlns:xsi=3D"http://www.w3.org/2000/10/XMLSchema-instance">
     <service name=3D"StringArrayServer" provider=3D"java:RPC">
                 <parameter name=3D"scope" value=3D"request"/>
                 <parameter name=3D"className" =
value=3D"StringArrayServer"/>
                 <parameter name=3D"allowedMethods" value=3D"*"/>
         </service>
</deployment>


The two versions of Axis generate nearly identical WSDL files for the=20
services via the ?wsdl query in the URL.

When a request is made, Axis 1.1 returns this XML:

<?xml version=3D"1.0" encoding=3D"UTF-8"?>
<soapenv:Envelope
xmlns:soapenv=3D"http://schemas.xmlsoap.org/soap/envelope/"=20
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema"=20
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance">
         <soapenv:Body>
                 <ns1:getStringArrayResponse=20
soapenv:encodingStyle=3D"http://schemas.xmlsoap.org/soap/encoding/"=20
xmlns:ns1=3D"http://DefaultNamespace">
                         <ns1:getStringArrayReturn
xsi:type=3D"soapenc:Array"=20
soapenc:arrayType=3D"xsd:string[3]"=20
xmlns:soapenc=3D"http://schemas.xmlsoap.org/soap/encoding/">
                                 <item>string 1</item>
                                 <item>string 2</item>
                                 <item>string 3</item>
                         </ns1:getStringArrayReturn>
                 </ns1:getStringArrayResponse>
         </soapenv:Body>
</soapenv:Envelope>

Axis 1.2 returns this XML, which fails to work with a .NET client built=20
from the WSDL generated by the ?wsdl comand:

<?xml version=3D"1.0" encoding=3D"utf-8"?>
<soapenv:Envelope
xmlns:soapenv=3D"http://schemas.xmlsoap.org/soap/envelope/"=20
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema"=20
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance">
         <soapenv:Body>
                 <ns1:getStringArrayResponse=20
soapenv:encodingStyle=3D"http://schemas.xmlsoap.org/soap/encoding/"=20
xmlns:ns1=3D"http://DefaultNamespace">
                         <getStringArrayReturn=20
soapenc:arrayType=3D"soapenc:string[3]" xsi:type=3D"soapenc:Array"=20
xmlns:soapenc=3D"http://schemas.xmlsoap.org/soap/encoding/">
                                 <getStringArrayReturn=20
xsi:type=3D"soapenc:string">string 1</getStringArrayReturn>
                                 <getStringArrayReturn=20
xsi:type=3D"soapenc:string">string 2</getStringArrayReturn>
                                 <getStringArrayReturn=20
xsi:type=3D"soapenc:string">string 3</getStringArrayReturn>
                         </getStringArrayReturn>
                 </ns1:getStringArrayResponse>
         </soapenv:Body>
</soapenv:Envelope>

Is this considered a bug or just the new intended behavior?

Thanks,

Andrew


At 10:48 AM 6/22/2005, you wrote:
>Oliver,
>
>I think I have a problem similar to yours.  I had an RPC service
written=20
>in Java from which I generated WSDL that was consumed by a .NET=20
>client.  The client is in use, so I can't change the interface=20
>now.  Upgrading to Axis 1.2 from 1.1 changes how arrays of Strings get=20
>returned to the .NET client--so I can't upgrade to Axis 1.2 without=20
>breaking the current system and making changes on the client.  Like
you, I=20
>know I'm doing things somewhat backward (going from Java to WSDL rather

>than the other way around).  Is backward compatibility for this sort of

>scenario simply not a goal of Axis?  Can any developers comment?
>
>Thanks,
>
>Andrew
>
>
>***original message***
>
>Hi Dims,
>
>thanks for your answer. I think that there is already a bug report for=20
>this bug (if \
>it's stil present). I'm not sure but maybe I'm doing something bad with
my \
>deployment. The problem is: The webservices I'm working on are
generated=20
>from \
>CORBA-IDL - not from a WSDL as I have explained in my mail "AXIS 1.2
and=20
>MS VB \
>interop (arrays)" So the way it goes is CORBA-IDL -> idlj-> Java-Stubs
->=20
>deploy as \
>WS -> generate WSDL -> generate Client-Stub.
>
>The generated WSDL is (the "getUserDomainsByName"-Methode returning an=20
>Array of \
>"TDomain" makes trouble):