and I really appreciate your help
Vivek
From: Dan Christopherson <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: AXIS "interoperability" question [It is indeed
questionable]
Date: Fri, 27 Feb 2004 20:03:28 -0600
I'm not going to tell you t
IL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: AXIS "interoperability" question [It is indeed
questionable]
Date: Fri, 27 Feb 2004 20:03:28 -0600
I'm not going to tell you that WS Interoperability is a mature feature of
any web service toolkit; rather, they all have problems r
eroperability of Axis solutions limited to
basic data types like int, string and arrays"?
Vivek
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: AXIS interoperability question
Date: Fri, 27 Feb 2004 15:23:05 -0500
The client should generate their o
PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: AXIS interoperability question
Date: Fri, 27 Feb 2004 15:23:05 -0500
The client should generate their own stub classes (or whatever the .NET
equivelant is) based on the generated WSDL. The
serialization/deserialization proc
AIL PROTECTED]>
<[EMAIL PROTECTED] cc:
.com> Subject: AXIS int
Title: Message
Hi,
If I
have implemented web service provider using AXIS and also used custom
serialization / deserialization (based on AXIS specific serialization) does the
client always needs AXIS specific serialization / deserialization? How does this
work with a .NET client or client us
