OTE-SOAP-2508/#_Toc478383515
Best regards,
Anne
-Original Message-
From: Anand Natrajan [mailto:[EMAIL PROTECTED]
Sent: Friday, August 13, 2004 11:51 AM
To: [EMAIL PROTECTED]
Subject: Re: Serialization error with Axis1.2 rpc/encoded service and
gSOAP
Shashi,
I am very familiar with that probl
ces, but you shouldn't
be building new rpc/encoded applications. SOAP encoding is a dead-end
technology.
[1] http://www.w3.org/TR/2000/NOTE-SOAP-2508/#_Toc478383515
Best regards,
Anne
-Original Message-----
From: Anand Natrajan [mailto:[EMAIL PROTECTED]
Sent: Friday, August 13,
[mailto:[EMAIL PROTECTED]
Sent: Friday, August 13, 2004 8:51 AM
To: [EMAIL PROTECTED]
Subject: Re: Serialization error with Axis1.2 rpc/encoded service and gSOAP
Shashi,
I am very familiar with that problem (I entered the bug report to which you
allude in your email). Yes, this is a serious
Shashi,
I am very familiar with that problem (I entered the bug report to which you
allude in your email). Yes, this is a serious interoperability problem.
However, I now agree with Davanum Srinivas that Axis 1.2 is actually doing
the correct thing when it assigns the soapenc namespace to string.
Title: Message
Hi
All,
I have been using
Axis1.1 on server and gSOAP on the client for long time and everything has been
working fine. I am trying to migrate to Axis1.2 and picked up bits on Aug5. When
I tried to generate header and stubs and compile the client project, it failed.
After f
