Return-Path: Mailing-List: contact soap-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list soap-dev@xml.apache.org Received: (qmail 6452 invoked from network); 7 Nov 2000 01:31:23 -0000 Received: from unknown (HELO mail.montana.boreham.org) (63.112.219.168) by locus.apache.org with SMTP; 7 Nov 2000 01:31:23 -0000 Received: from cheeto ([63.112.219.176]) by mail.montana.boreham.org with Microsoft SMTPSVC(5.0.2195.1600); Mon, 6 Nov 2000 17:31:17 -0800 Message-ID: <07b401c0485a$6cad5810$b0db703f@mtbrook.boreham.org> From: "David Boreham" To: Subject: Problem with base64 encoded parameter value? Date: Mon, 6 Nov 2000 17:31:17 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_07B1_01C04817.5E6CF320" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 X-OriginalArrivalTime: 07 Nov 2000 01:31:17.0350 (UTC) FILETIME=[6CA6C860:01C0485A] X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. ------=_NextPart_000_07B1_01C04817.5E6CF320 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'm seeing some kind of problem with the decoding of base64-encoded = parameters in version 2.0. Specifically, this: dGVzdAp0ZXN0Mg=3D=3D fails while this: test works. The client is SOAP::Lite 0.41 By "fails" I mean that the SOAP servlet never calls the interface implementation class. It does in the "working" case. I've not yet attempted any further diagnosis, not tried a different client. Before I dive into this, I wanted to ping the dev community to see if a) it's a known problem and b) if I should be trying some newer code (from CVS ??) to see if the problem is still in the latest code. Thanks, and apologies if this was discussed in the past here, I don't have the bandwidth to read every single message. ------=_NextPart_000_07B1_01C04817.5E6CF320 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

I'm seeing some kind of problem with = the decoding=20 of base64-encoded parameters

in version 2.0. Specifically, = this:

<c-gensym5=20 xsi:type=3D"SOAP-ENC:base64">dGVzdAp0ZXN0Mg=3D=3D</c-gensym5>

fails while this:

<c-gensym5=20 xsi:type=3D"xsd:string">test</c-gensym5>

works.

The client is SOAP::Lite = 0.41

By "fails" I mean that the SOAP servlet = never calls=20 the interface

implementation class. It does in the = "working"=20 case. I've not yet

attempted any further diagnosis, not = tried a=20 different client.

Before I dive into this, I wanted to = ping the dev=20 community to see

if a) it's a known problem and b) if I = should be=20 trying some newer

code (from CVS ??) to see if the = problem is still=20 in the latest code.

Thanks, and apologies if this was = discussed in the=20 past here,

I don't have the bandwidth to read = every single=20 message.

------=_NextPart_000_07B1_01C04817.5E6CF320--