Hello all,
I have a really simple SOAP server that I've been using to debug some
incompatilibity problems between SOAP::Lite for PERL and Apache SOAP. What
appears to be happening is Apache SOAP is creating a SOAP document that it
claims is encoded using SOAP 1.1, when in fact it's encoded using
restricted in that
manner for 1.1).
-- Marc
-Original Message-----
From: Marc Tremblay [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 27, 2001 10:38 AM
To: Soap-Dev
Subject: Wrong encodingStyle being sent for boolean encoding.
Hello all,
I have a really simple SOAP server that I've been
Here's the patch Dave referred to previously (see "RE: do an Apache SOAP 2.3
release ?" 4/26/2002 in soap-dev).
It allows xsi:null="1" and xsi:null="true" to be properly handled by
refactoring the 0/1/true/false handling code in BooleanDeserializer into a
new method in SoapEncUtils called decodeB
