cc:
Subject: Re: AXIS/SOAP Interop Test
Summary
02/06/2002 1
R J Scheuerle wrote:
>
> i) Sending type="ArrayOfSOAPStruct" over the wire may be 'more correct' but
> is less interoperable. So I think we should continue to send type="soapenc:Array"
> over the wire...but I will make a comment in the array serializer explainly the
> pro's and con's.
+1
Ain't
To: [EMAIL PROTECTED]
US cc: [EMAIL PROTECTED]
Subject: Re: AXIS/SOAP Interop Test
Summary
IBMUScc:
Subject: Re: AXIS/SOAP Interop Test
Summary
-837)
e-mail: [EMAIL PROTECTED]
fax: +01-972-605-4071
___
-Original Message-
From: Sadiq, Waqar
Sent: Wednesday, February 06, 2002 9:34 AM
To: [EMAIL PROTECTED]
Cc: Scott Beaudreau
Subject: RE: AXIS/SOAP Interop Test Summary
That is true if
Waqar Sadiq wrote:
>
> That is true if your client is C# or VB program. You have greater control.
> However, if your client is a browser based program written in ASP.NET, you
> don't seem to have the same kind of control.
I have written ASP.Net programs using that attribute. But in any case, yo
R J Scheuerle wrote:
>
> I have some questions...
>
> So a runtime could send an array using "style A":
>
>
>
> Or a runtime could send an array using "style B":
>
>
>
> Apache SOAP is sending "style B"; I believe it used to send "style A".
> Apache Axis sends "style A".
Apache SOAP wi
11 AM
To: [EMAIL PROTECTED]
Subject: RE: AXIS/SOAP Interop Test Summary
Waqar Sadiq wrote:
>
> I was wondering if anyone has tested interoperability with .NET for
passing
> arrays. I had an EJB service which was deployed using axis. The method
> required an array of string parameter.
Ruby/Raleigh/IBM@To: [EMAIL PROTECTED]
IBMUScc:
Waqar Sadiq wrote:
>
> I was wondering if anyone has tested interoperability with .NET for passing
> arrays. I had an EJB service which was deployed using axis. The method
> required an array of string parameter. When I called it from .NET client,
> it defined the array as separate element and
, 2002 6:06 PM
To: [EMAIL PROTECTED]
Subject: Re: AXIS/SOAP Interop Test Summary
R J Scheuerle Jr wrote:
>
> You indicated yesterday that a change was made to Apache SOAP to
> register array types. I am concerned that they will run across this same
> problem...and from last night'
R J Scheuerle Jr wrote:
>
> You indicated yesterday that a change was made to Apache SOAP to
> register array types. I am concerned that they will run across this same
> problem...and from last night's test it appears that they did.
> See SOAP echoStructArray for SOAP RMI. Also, the SOAP echoStr
US cc:
Subject: AXIS/SOAP Interop Test
Summary
01/31/2002 0
cc:
Subject: Re: AXIS/SOAP Interop Test
Summary
01/31/2002 1
Rich Scheuerle Jr wrote:
>
> The number of red failures in the last run: 35
> The number of red failures in the jan 1 run: 41
Great work!
> Void (SoapX4 and TclSoap both return elements with no values)
Open question: should we accept these resposes?
We accept an response containing an empty en
The number of red failures in the last run: 35
The number of red failures in the jan 1 run: 41
Test Missing Service Other
---
Float 1 (TCLSoap returned correct value, but it's
a xsd:double)
Struct 1 (Soap
16 matches
Mail list logo
