Loading ...
Sorry, an error occurred while loading the content.

MS Toolkit 2.0 base64 compatibility, was How to get a response?

Expand Messages
  • Tom Mornini
    ... Aha! I ll have my guys look into that immediately. ... OK! I can see I ll need to experiment a bit, but that looks like just what the Dr. ordered! -- --
    Message 1 of 1 , Mar 18, 2002
    • 0 Attachment
      On Monday, March 18, 2002, at 09:26 AM, Paul Kulchenko wrote:

      >> Myself and others don't have any idea as to the compatibility
      >> between MS Toolkit 2.0 client and SOAP::Lite server with respect
      >> to base64 encoded fields.

      > As far as I remember you can force MS Toolkit to provide type
      > information on wire by using anyType type in service description, but
      > I'm not absolutely sure about that.

      Aha! I'll have my guys look into that immediately.

      > You can also provide custom deserializer in SOAP::Lite like this:
      >
      > BEGIN {
      > package MyDeserializer; use vars qw(@ISA);
      > @ISA = 'SOAP::Deserializer';
      > sub typecast {
      > my $self = shift;
      > return if ref $_[0]; # skip objects
      > return SOAP::XMLSchemaSOAP1_1::Deserializer->as_base64($_[0])
      > if $_[1] eq '{namespace}name';
      > # - or -
      > # if $_[1] eq 'name'; # if in no-namespace
      > }
      > }

      OK! I can see I'll need to experiment a bit, but that looks like
      just what the Dr. ordered!

      --
      -- Tom Mornini
      -- eWingz Systems, Inc.
      --
      -- ICQ: 113526784, AOL: tmornini, Yahoo: tmornini, MSN: tmornini
    Your message has been successfully submitted and would be delivered to recipients shortly.