Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@xml.apache.org
Message-ID: <038501c1fef3$882d4220$e0a3f40f@nordwand>
From: "Steve Loughran" <steve_l@iseran.com>
To: <axis-dev@xml.apache.org>
References: 
 <F504A8CEE925D411AF4A00508B8BE90A03B9A249@exna07.securitydynamics.com>
 <022701c1fe80$4aac4f40$e0a3f40f@nordwand>
 <fp0deuo4e0l2qv17v1s9rar9fhkpv997je@4ax.com>
Subject: Re: [BUG] Beta2 interop (was RE: Interoperability issue with
 MSVC++.Net)
Date: Sat, 18 May 2002 22:10:44 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: "Simon Fell" <soap@zaks.demon.co.uk>
To: <axis-dev@xml.apache.org>
Sent: Saturday, May 18, 2002 9:43 AM
Subject: Re: [BUG] Beta2 interop (was RE: Interoperability issue with
MSVC++.Net)


On Sat, 18 May 2002 08:25:49 -0700, in soap you wrote:

>>> SPROXY.EXE is the VC++.Net proxy generator that has trouble here.
>>> WSDL.EXE is able to operate without problems.
>>
>>sproxy? There is a third dotnet WSDL to code generator. Well I never. Two
>>SOAP stacks, three proxy generators... .NET must be the only framework to
>>have internal interop issues.
>>
>>-steve

>ROTFL !, sproxy.exe is the proxy generator for the SOAP support in
>ATL7, [native C++ code], rather than the managed platform [i guess
>that's the problem when you stick .NET on the end of everything], so
>that's actually 3 soap stacks, and 3 proxy generators.

and then there is msstk, a beta of v3 of which just came out ...

>There's no ATL server in the soapbuilders interop anymore, but i seem
>to recall it had a few issues. Given that's its not getting any
>interop testing, i wouldn't go near it.

Simon, can you see from your server's access logs, what systems are running
interop tests against it? do you see any from the new Sun 'reference
implementation', for example?

-steve


Cheers
Simon