From xmlrpcmelendeztammy@example.org Wed May 03 10:52:05 2006 Return-Path: <xmlrpcmelendeztammy@example.org> Delivered-To: melendeztammy@example.org Received: (qmail 66666 invoked from network); 3 May 2006 10:52:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 May 2006 10:52:05 -0000 Received: (qmail 49537 invoked by uid 500); 3 May 2006 10:52:04 -0000 Delivered-To: melendeztammy@example.org Received: (qmail 49518 invoked by uid 500); 3 May 2006 10:52:04 -0000 Mailing-List: contact melendeztammy@example.org; run by ezmlm Precedence: bulk list-help: <mailto:melendeztammy@example.org> list-unsubscribe: <mailto:melendeztammy@example.org> List-Post: <mailto:melendeztammy@example.org> Reply-To: melendeztammy@example.org List-Id: <xmlrpc-dev.ws.apache.org> Delivered-To: mailing list melendeztammy@example.org Delivered-To: moderator for melendeztammy@example.org Received: (qmail 40155 invoked by uid 99); 3 May 2006 09:40:06 -0000 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) From: <melendeztammy@example.org> Sender: "y.turban" <melendeztammy@example.org> To: <melendeztammy@example.org> Subject: Date and unicode handling in 3.0b1 Date: Wed, 3 May 2006 12:39:13 +0300 Organization: btis Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAATXA5tXK1UEedLOvAFHRJksKAAAAQAAAAsoBEfMSGHEG9xZjSmelendeztammy@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcZulXAvxtAf78wXRmu1a1j54ijo8w== X-Virus-Scanned: melendeztammy@example.org X-Virus-Scanned: by melendeztammy@example.org X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N My work on the current project made me really appreciate the simplicity and power of this protocol, and for this I'm really grateful to Jochen and all of you guys who took the time to develop this library. Thank you, and keep up the good job ! I've been developing the client java application which has to RPC delphi-based server. This is a multi-language project, so all the communication has to go in utf-8. I do understand that my requirements are far from common, but because of these requirements I was lucky to find some issues ( most of them traced to ws.commons.util ) which could be resolved in next version. Environment : Client : windows xp java 1.5 xmlrpc-3.0b1-SNAPSHOT Server : delphi 7.0 on Windows xp or kylix 3.0 on linux xml-rpc library from http://sourceforge.net/projects/delphixml-rpc/ 1. org.apache.xmlrpc.parser.DateParser throws SAXParseException("Failed to parse integer value: " ), which is a little bit misleading since it is DATE value it tries to parse. This probably should be changed to "Failed to parse date value" 2. org.apache.ws.commons.util.XsDateTimeFormat simply does not work with dates in 19980717T14:08:55 format, as described in XMLRPC specification. I had to change the source to make it understand iso8601. Would it be possible to add some configuration parameter to ws.commons.util, so it could handle the expected date format ? 3. org.apache.xmlrpc.test.BaseTest does not have any tests to demonstrate handling of date objects, that's why issues 1 and 2 weren't caught at the testing stage. I think it would be useful to unclude date tests in future versions. 4. org.apache.ws.commons.serialize.XMLWriterImpl encodes utf-8 characters as &#code;&#code;.... which causes trouble on the server side. I do not think that there should be any special handling of unicode characters at all, since - xmlrpc uses utf-8 encoding of the request by default - encoding bloats up the size of xml requests ( 7 encoded characters for each non-encoded one ) - encoding takes up additional resources - encoding causes incompatibilities on the server side ( i.e. delphixmlrpc ) The way to get rid of the encoding would be modify canEncode function in XMLWriterImpl to always return true. All this leads me to question the benefits of building future versions of xmlrpc based on ws.common.util . Is the functionality delegated there really so big, as to justify the need for additional resources to test and integrate this library ? I would appreciate your comments. From xmlrpcmelendeztammy@example.org Wed May 03 11:02:13 2006 Return-Path: <xmlrpcmelendeztammy@example.org> Delivered-To: melendeztammy@example.org Received: (qmail 72362 invoked from network); 3 May 2006 11:02:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 May 2006 11:02:13 -0000 Received: (qmail 69800 invoked by uid 500); 3 May 2006 11:02:12 -0000 Delivered-To: melendeztammy@example.org Received: (qmail 69776 invoked by uid 500); 3 May 2006 11:02:11 -0000 Mailing-List: contact melendeztammy@example.org; run by ezmlm Precedence: bulk list-help: <mailto:melendeztammy@example.org> list-unsubscribe: <mailto:melendeztammy@example.org> List-Post: <mailto:melendeztammy@example.org> Reply-To: melendeztammy@example.org List-Id: <xmlrpc-dev.ws.apache.org> Delivered-To: mailing list melendeztammy@example.org Received: (qmail 69767 invoked by uid 99); 3 May 2006 11:02:11 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 May 2006 04:02:11 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of melendeztammy@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO ug-out-1314.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 May 2006 04:02:11 -0700 Received: by ug-out-1314.google.com with SMTP id a2so48296ugf for <melendeztammy@example.org>; Wed, 03 May 2006 04:01:49 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=dyU8t/mtTXnpVTxDNhCDNmQ+8z5TWhESoax9ZIALAr2EC/nYhw1Hoi7KfT2uh5VT9Tw+dEbYZrJydTqago9emY61JJKqDPHmLkWNU9sXlAuroKdUFT9Olvwq5hYYmq2nKpdEgDFmmUo4ydzUAyO0tdGoZYGKzm52C6evoqoOTWU= Received: by 83.161.120.155 with SMTP id q1mr36622huq; Wed, 03 May 2006 04:01:49 -0700 (PDT) Received: by 83.161.120.155 with HTTP; Wed, 3 May 2006 04:01:49 -0700 (PDT) Message-ID: <melendeztammy@example.org> Date: Wed, 3 May 2006 13:01:49 +0200 From: "Jochen Wiedmann" <melendeztammy@example.org> To: melendeztammy@example.org, melendeztammy@example.org Subject: Re: Date and unicode handling in 3.0b1 In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAATXA5tXK1UEedLOvAFHRJksKAAAAQAAAAOW8BlqPHf0WOmUF27WNtmQEAAAAA@btis.by> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAATXA5tXK1UEedLOvAFHRJksKAAAAQAAAAOW8BlqPHf0WOmUF27WNtmQEAAAAA@btis.by> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 5/3/06, melendeztammy@example.org <melendeztammy@example.org> wrote: Hi, first of all, a hint: Please be so kind and do not crosspost to multiple lists. Use the list which you find most appropriate. In this case I have choosen xmlrpc-dev for the reply. > 1. org.apache.xmlrpc.parser.DateParser throws SAXParseException("Failed t= o > parse integer value: " ), which is a little bit misleading since it is DA= TE > value it tries to parse. This probably should be changed to "Failed to pa= rse > date value" Patches welcome. :-) > 2. org.apache.ws.commons.util.XsDateTimeFormat simply does not work with > dates in 19980717T14:08:55 format, as described in XMLRPC specification. = I > had to change the source to make it understand iso8601. Would it be possi= ble > to add some configuration parameter to ws.commons.util, so it could handl= e > the expected date format ? Again, a patch would be welcome, at least a patch to the test suite of ws-commons-util, which demonstrates the problem. > 3. org.apache.xmlrpc.test.BaseTest does not have any tests to demonstrate > handling of date objects, that's why issues 1 and 2 weren't caught at the > testing stage. I think it would be useful to unclude date tests in future > versions. Is that so? That's of course, not good. How about yet another patch? :-))) > 4. org.apache.ws.commons.serialize.XMLWriterImpl encodes utf-8 characters= as > &#code;&#code;.... which causes trouble on the server side. I do not thin= k > that there should be any special handling of unicode characters at all, > since > - xmlrpc uses utf-8 encoding of the request by default > - encoding bloats up the size of xml requests ( 7 encoded charact= ers > for each non-encoded one ) > - encoding takes up additional resources > - encoding causes incompatibilities on the server side ( i.e. > delphixmlrpc ) > The way to get rid of the encoding would be modify canEncode function in > XMLWriterImpl to always return true. > > All this leads me to question the benefits of building future versions of > xmlrpc based on ws.common.util . Is the functionality delegated there rea= lly > so big, as to justify the need for additional resources to test and > integrate this library ? First of all, your requirements seem to be quite unusual: I have met XML parsers, which are unable to deal with Unicode characters, but I have never met XML parsers, which are unable to deal with character escape sequences? The particular XMLWriter instance was choosen because it is (in the light of the above paragraph) the best thing in terms of portability. I agree with you, that this is possibly not optimal in terms of performance. However, there are multiple XMLWriter instances (in particular the RawXMLWriter, which should do exactly what you want.) and the XML-RPC framework should allow you to use a different implementation by supplying another XMLWriterFactory. Did you consider using that? Jochen -- Whenever you find yourself on the side of the majority, it is time to pause and reflect. (Mark Twain) From xmlrpcmelendeztammy@example.org Fri May 05 09:31:40 2006 Return-Path: <xmlrpcmelendeztammy@example.org> Delivered-To: melendeztammy@example.org Received: (qmail 8321 invoked from network); 5 May 2006 09:31:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 May 2006 09:31:38 -0000 Received: (qmail 39005 invoked by uid 500); 5 May 2006 09:31:37 -0000 Delivered-To: melendeztammy@example.org Received: (qmail 38930 invoked by uid 500); 5 May 2006 09:31:36 -0000 Mailing-List: contact melendeztammy@example.org; run by ezmlm Precedence: bulk list-help: <mailto:melendeztammy@example.org> list-unsubscribe: <mailto:melendeztammy@example.org> List-Post: <mailto:melendeztammy@example.org> Reply-To: melendeztammy@example.org List-Id: <xmlrpc-dev.ws.apache.org> Delivered-To: mailing list melendeztammy@example.org Received: (qmail 38873 invoked by uid 99); 5 May 2006 09:31:36 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 May 2006 02:31:36 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of melendeztammy@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO py-out-1112.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 May 2006 02:31:34 -0700 Received: by py-out-1112.google.com with SMTP id x66so113779pye for <melendeztammy@example.org>; Fri, 05 May 2006 02:31:14 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=h3O9lsVpWTrY8JWNmK/DiKr6aw29Uqs0qsD8VMlT+AXjKvcsTMSu3P4w5wLUr6I4xJND1kLHXNlQkvrxQGrlyHnROILcO/GYh/ltiafQyeeDYhnzXT5/S2qWT10l5R1+TQ1rm1eJU9SkQpfsN/IrLAWC923GB2/1TgQq097vEZQ= Received: by 83.161.120.155 with SMTP id f18mr475333pyk; Fri, 05 May 2006 02:31:12 -0700 (PDT) Received: by 83.161.120.155 with HTTP; Fri, 5 May 2006 02:31:12 -0700 (PDT) Message-ID: <melendeztammy@example.org> Date: Fri, 5 May 2006 11:31:12 +0200 From: "Henri Gomez" <melendeztammy@example.org> To: melendeztammy@example.org Subject: xmlrpc 3.0 a2 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi to all, Wonder when we could have an update of the XMLRPC 3.0 (a2 ?). Many fixes were applied till 3.0-a1 and it may be good to have a fresh release to make tests ? Regards From xmlrpcmelendeztammy@example.org Fri May 05 11:13:53 2006 Return-Path: <xmlrpcmelendeztammy@example.org> Delivered-To: melendeztammy@example.org Received: (qmail 57570 invoked from network); 5 May 2006 11:13:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 May 2006 11:13:52 -0000 Received: (qmail 60843 invoked by uid 500); 5 May 2006 11:13:52 -0000 Delivered-To: melendeztammy@example.org Received: (qmail 60816 invoked by uid 500); 5 May 2006 11:13:51 -0000 Mailing-List: contact melendeztammy@example.org; run by ezmlm Precedence: bulk list-help: <mailto:melendeztammy@example.org> list-unsubscribe: <mailto:melendeztammy@example.org> List-Post: <mailto:melendeztammy@example.org> Reply-To: melendeztammy@example.org List-Id: <xmlrpc-dev.ws.apache.org> Delivered-To: mailing list melendeztammy@example.org Received: (qmail 60798 invoked by uid 99); 5 May 2006 11:13:51 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 May 2006 04:13:51 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of melendeztammy@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO ug-out-1314.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 May 2006 04:13:49 -0700 Received: by ug-out-1314.google.com with SMTP id j40so478092ugd for <melendeztammy@example.org>; Fri, 05 May 2006 04:13:28 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Rc7lT4TCXSMuli84KwCS2fa8dTeQw5ouvIGFSBznx6hu82uC6/T+f0rPbtCOVmNIXHaDa6uujP/SMRz3skGkFV4c+mQKJqipD8KvR8pGhii6oAFffYR9OCN9AwDw8xQlEscMmF9acB5wtWUoSuI5Fqanr3pcmJ0TQAY808VQ2Io= Received: by 83.161.120.155 with SMTP id s13mr251426hus; Fri, 05 May 2006 04:13:28 -0700 (PDT) Received: by 83.161.120.155 with HTTP; Fri, 5 May 2006 04:13:28 -0700 (PDT) Message-ID: <melendeztammy@example.org> Date: Fri, 5 May 2006 13:13:28 +0200 From: "Jochen Wiedmann" <melendeztammy@example.org> To: melendeztammy@example.org Subject: Re: xmlrpc 3.0 a2 In-Reply-To: <melendeztammy@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <melendeztammy@example.org> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 5/5/06, Henri Gomez <melendeztammy@example.org> wrote: > Wonder when we could have an update of the XMLRPC 3.0 (a2 ?). > > Many fixes were applied till 3.0-a1 and it may be good to have a fresh > release to make tests ? Volunteer to do the job? :-) -- Whenever you find yourself on the side of the majority, it is time to pause and reflect. (Mark Twain) From xmlrpcmelendeztammy@example.org Fri May 05 11:18:57 2006 Return-Path: <xmlrpcmelendeztammy@example.org> Delivered-To: melendeztammy@example.org Received: (qmail 59782 invoked from network); 5 May 2006 11:18:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 May 2006 11:18:57 -0000 Received: (qmail 65498 invoked by uid 500); 5 May 2006 11:18:56 -0000 Delivered-To: melendeztammy@example.org Received: (qmail 65467 invoked by uid 500); 5 May 2006 11:18:56 -0000 Mailing-List: contact melendeztammy@example.org; run by ezmlm Precedence: bulk list-help: <mailto:melendeztammy@example.org> list-unsubscribe: <mailto:melendeztammy@example.org> List-Post: <mailto:melendeztammy@example.org> Reply-To: melendeztammy@example.org List-Id: <xmlrpc-dev.ws.apache.org> Delivered-To: mailing list melendeztammy@example.org Received: (qmail 65454 invoked by uid 99); 5 May 2006 11:18:56 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 May 2006 04:18:56 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of melendeztammy@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO py-out-1112.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 May 2006 04:18:55 -0700 Received: by py-out-1112.google.com with SMTP id x66so131946pye for <melendeztammy@example.org>; Fri, 05 May 2006 04:18:34 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=WnBw4rjj0QoFNqAvhgcg8t1z0TOzG6uwB4U8CAWp5UfAYSckkTDgvNi/4WRQ242OufT5Xmb6mUetJPXH16oxuygH6HndSyaHK2gNB9S/rv9al/evGA9r+SgMm4UZ1Tm+utJ1r6UxEh4FCh4zV70tb8Dy5k0Y1CgKMHvvaiCtTNs= Received: by 83.161.120.155 with SMTP id b5mr564625pym; Fri, 05 May 2006 04:18:34 -0700 (PDT) Received: by 83.161.120.155 with HTTP; Fri, 5 May 2006 04:18:34 -0700 (PDT) Message-ID: <melendeztammy@example.org> Date: Fri, 5 May 2006 13:18:34 +0200 From: "Henri Gomez" <melendeztammy@example.org> To: melendeztammy@example.org Subject: Re: xmlrpc 3.0 a2 In-Reply-To: <melendeztammy@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <melendeztammy@example.org> <melendeztammy@example.org> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N You're kidding ? :) 2006/5/5, Jochen Wiedmann <melendeztammy@example.org>: > On 5/5/06, Henri Gomez <melendeztammy@example.org> wrote: > > > Wonder when we could have an update of the XMLRPC 3.0 (a2 ?). > > > > Many fixes were applied till 3.0-a1 and it may be good to have a fresh > > release to make tests ? > > Volunteer to do the job? :-) > > -- > Whenever you find yourself on the side of the > majority, it is time to pause and reflect. > (Mark Twain) > From xmlrpcmelendeztammy@example.org Fri May 05 21:18:14 2006 Return-Path: <xmlrpcmelendeztammy@example.org> Delivered-To: melendeztammy@example.org Received: (qmail 87093 invoked from network); 5 May 2006 21:18:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 May 2006 21:18:12 -0000 Received: (qmail 4994 invoked by uid 500); 5 May 2006 21:18:07 -0000 Delivered-To: melendeztammy@example.org Received: (qmail 4942 invoked by uid 500); 5 May 2006 21:18:05 -0000 Mailing-List: contact melendeztammy@example.org; run by ezmlm Precedence: bulk list-help: <mailto:melendeztammy@example.org> list-unsubscribe: <mailto:melendeztammy@example.org> List-Post: <mailto:melendeztammy@example.org> Reply-To: melendeztammy@example.org List-Id: <xmlrpc-dev.ws.apache.org> Delivered-To: mailing list melendeztammy@example.org Received: (qmail 4932 invoked by uid 99); 5 May 2006 21:18:05 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 May 2006 14:18:05 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of melendeztammy@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO ug-out-1314.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 May 2006 14:18:04 -0700 Received: by ug-out-1314.google.com with SMTP id j40so707511ugd for <melendeztammy@example.org>; Fri, 05 May 2006 14:17:43 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=nlIoqKXKj9L57zX7TqGnozqQX9P7KTEY3JvH62EusNlAJDId+Z1tMJ4ajLfGV98JUNu3VoKP+i6kOEI4Qk3Vex8ldnIC9oIOShVlE3/JlxGpc6mUSfwLmJPn3sMW++aO7xuKshiXTCRbIxi6NI5mVgthdr/NBp8tXNkYhLPPRp0= Received: by 83.161.120.155 with SMTP id z17mr177455huz; Fri, 05 May 2006 14:17:43 -0700 (PDT) Received: by 83.161.120.155 with HTTP; Fri, 5 May 2006 14:17:43 -0700 (PDT) Message-ID: <melendeztammy@example.org> Date: Fri, 5 May 2006 23:17:43 +0200 From: "Jochen Wiedmann" <melendeztammy@example.org> To: melendeztammy@example.org Subject: Re: xmlrpc 3.0 a2 In-Reply-To: <melendeztammy@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <melendeztammy@example.org> <melendeztammy@example.org> <melendeztammy@example.org> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 5/5/06, Henri Gomez <melendeztammy@example.org> wrote: > You're kidding ? :) You're asking. :-) -- Whenever you find yourself on the side of the majority, it is time to pause and reflect. (Mark Twain) From xmlrpcmelendeztammy@example.org Sun May 07 20:45:03 2006 Return-Path: <xmlrpcmelendeztammy@example.org> Delivered-To: melendeztammy@example.org Received: (qmail 60432 invoked from network); 7 May 2006 20:45:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 7 May 2006 20:45:03 -0000 Received: (qmail 65672 invoked by uid 500); 7 May 2006 20:45:03 -0000 Delivered-To: melendeztammy@example.org Received: (qmail 65512 invoked by uid 500); 7 May 2006 20:45:02 -0000 Mailing-List: contact melendeztammy@example.org; run by ezmlm Precedence: bulk list-help: <mailto:melendeztammy@example.org> list-unsubscribe: <mailto:melendeztammy@example.org> List-Post: <mailto:melendeztammy@example.org> Reply-To: melendeztammy@example.org List-Id: <xmlrpc-dev.ws.apache.org> Delivered-To: mailing list melendeztammy@example.org Received: (qmail 65503 invoked by uid 99); 7 May 2006 20:45:01 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 May 2006 13:45:01 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 May 2006 13:45:01 -0700 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id C523C7142C4 for <melendeztammy@example.org>; Sun, 7 May 2006 20:44:21 +0000 (GMT) Message-ID: <18577114.1147034661805.JavaMail.jira@brutus> Date: Sun, 7 May 2006 20:44:21 +0000 (GMT+00:00) From: "Jochen Wiedmann (JIRA)" <melendeztammy@example.org> To: melendeztammy@example.org Subject: [jira] Geschlossen: (XMLRPC-79) Problems when enabling gzip compression In-Reply-To: <154871172.1144760062417.JavaMail.jira@ajax> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/XMLRPC-79?page=all ] Jochen Wiedmann closed XMLRPC-79: --------------------------------- Resolution: Fixed Finally found out the deeper reason: The HTTP/1.0 specification requires a content-length header. As shown in Bugzilla 39508, there is a bug in Tomcat, which causes Tomcat to handle such requests incorrectly: Tomcat should simply refuse the request with an HTTP status code 400 (invalid). However, Tomcat accepts the request, but drops the request body. The absence of the request body explains the error message: The XML parser receives no data. As support of HTTP/1.1 with the Lite HTTP transport wouldn't be that easy (requires reading of chunked encoding on the client side), I have choosen to reject dropping the content-length header (and hence the support for gzip encoding) with the lite http transport. > Problems when enabling gzip compression > --------------------------------------- > > Key: XMLRPC-79 > URL: http://issues.apache.org/jira/browse/XMLRPC-79 > Project: XML-RPC > Type: Bug > Components: Releases > Versions: 3.0a1 > Environment: Linux Red Hat > Java 1.4.2 and 1.5(1.5.0_06) > Apache Tomcat 5.0.19, 5.5.9 > Reporter: Inaki Ortiz > Assignee: Jochen Wiedmann > Attachments: MyXmlRpcClient.java > > I am having problems when enabling the request/response compression > mode. I am using xmlrpc-3.0a1.jar for both my client and my server. In > the client I run the following: > config = new XmlRpcClientConfigImpl(); > config.setServerURL(serverURL); > // enables faster and memory saving streaming mode > config.setContentLengthOptional(true); > // enable vendor extensions to allow compression, data types support ... > config.setEnabledForExtensions(true); > config.setGzipCompressing(true); // requests gzip compression > config.setGzipRequesting(true); // requests server to gzip response > > client = new XmlRpcClient(); > client.setConfig(config); > client.execute(...) > [...] > In the server I make use of the XmlRpcServlet class > (org.apache.xmlrpc.webserver package) embedded into Tomcat 5 and I have > set enabledForExtensions to true within the init parameters of the > servlet (web.xml file) > When I run a dummy request as it is described in the code above I get > the following exception: > org.apache.xmlrpc.XmlRpcException: Failed to parse XML-RPC request: > Content is not allowed in prolog. > at org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse > (XmlRpcStreamTransport.java:274) > at org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest > (XmlRpcStreamTransport.java:216) > at org.apache.xmlrpc.client.XmlRpcClientWorker.execute > (XmlRpcClientWorker.java:53) > at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:166) > at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:136) > at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:125) > at esavo.voql.xmlrpc.MyXmlRpcClient.execute(MyXmlRpcClient.java:54) > at esavo.voql.xmlrpc.MyXmlRpcClient.main(MyXmlRpcClient.java:74) > If I comment the gzip compression out, both on the request and the > response, my test works fine: > config = new XmlRpcClientConfigImpl(); > config.setServerURL(serverURL); > // enables faster and memory saving streaming mode > config.setContentLengthOptional(true); > // enable vendor extensions to allow compression, data types support ... > config.setEnabledForExtensions(true); > client = new XmlRpcClient(); > client.setConfig(config); > client.execute(...) > [...] > The complete source code is the following: > 1. Client Side > ------------------------- > package esavo.voql.xmlrpc; > import java.net.URL; > import org.apache.xmlrpc.*; > import org.apache.xmlrpc.client.*; > /** > * MyXmlRpcClient > * @author Inaki Ortiz de Landaluce Saiz - ESAC/ESA - Madrid, Spain > */ > public class MyXmlRpcClient { > > /** XMLRpcClientConfig instance to specify serverURL, credentials ...etc */ > private XmlRpcClientConfigImpl config; > /** The XmlRpcClient itself */ > private XmlRpcClient client; > > /** > * Creates a new instance of MyXmlRpcClient > */ > public MyXmlRpcClient(URL serverURL) { > // Step 1: Instances the client configuration and sets some properties > // N.B: This should be configurable through a xml or properties file > > config = new XmlRpcClientConfigImpl(); > config.setServerURL(serverURL); > // enables faster and memory saving streaming mode > config.setContentLengthOptional(true); > // enable vendor extensions to allow compression, data types support ... > config.setEnabledForExtensions(true); > // it works fine when the following two lines are commented > config.setGzipCompressing(true); // requests gzip compression > config.setGzipRequesting(true); // requests server to gzip response > > // Step 2: Instances the client and atttaches the configuration to it > > client = new XmlRpcClient(); > client.setConfig(config); > // sets the fastest transport factory. > // There are several transport factories available: > // XmlRpcSunHttpTransportFactory - Uses default HTTP connection > // XmlRpcCommonsTransportFactory - Jakarta commons, lower memory profile > // XmlRpcLiteHttpTransportFactory - Faster, does not support HTTP/1.1</ul> > client.setTransportFactory(new XmlRpcLiteHttpTransportFactory(client)); > } > > /** > * Executes an XML-RPC call > * @param methodName The method being performed. > * @param method The parameters. > * @return The result object > */ > public Object execute(String methodName, Object[] params) throws XmlRpcException { > return client.execute(methodName, params); > } > > /** > * Returns XmlRpcClient instance > */ > public XmlRpcClient getClient() { > return client; > } > > public static void main(String[] args) { > String serverStr = "http://localhost:8084/VOQL-server/servlet/xmlrpc"; > try { > URL serverURL = new URL(serverStr); > MyXmlRpcClient client = new MyXmlRpcClient(serverURL); > > // full check disabled > Object[] params = new Object[]{new Boolean(false)}; > Boolean result = (Boolean) client.execute("Status.check", params); > System.out.println("Result is " + result.toString()); > } catch (XmlRpcClientException e) { > e.printStackTrace(); > } catch (Exception e) { > e.printStackTrace(); > } > } > } > 2. Server Side > -------------------------- > 2.1 WAR configuration file (web.xml) > ------------------------------------------------------------------- > <?xml version="1.0" encoding="UTF-8"?> > <web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"> > <servlet> > <servlet-name>XmlRpcServlet</servlet-name> > <servlet-class>org.apache.xmlrpc.webserver.XmlRpcServlet</servlet-class> > <init-param> > <param-name>enabledForExtensions</param-name> > <param-value>true</param-value> > </init-param> > </servlet> > <servlet-mapping> > <servlet-name>XmlRpcServlet</servlet-name> > <url-pattern>/servlet/xmlrpc</url-pattern> > </servlet-mapping> > <session-config> > <session-timeout> > 30 > </session-timeout> > </session-config> > <welcome-file-list> > <welcome-file> > index.jsp > </welcome-file> > </welcome-file-list> > </web-app> > 2.2 Handler > ----------------------- > package esavo.voql.server; > /** > * > * @author Inaki Ortiz de Landaluce Saiz - ESAC/ESA - Madrid, Spain > */ > public class Status { > > /** Creates a new instance of Status */ > public Status() { > } > > public boolean check(boolean fullCheck) { > // perform a full check on service availability. TBD > if(!fullCheck) return true; > else return false; > } > > } > 2.3 XmlRpcServlet.properties > ---------------------------------------------------- > Remote=org.apache.xmlrpc.test.BaseTest$Remote > Status=esavo.voql.server.Status -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From xmlrpcmelendeztammy@example.org Sun May 07 20:49:14 2006 Return-Path: <xmlrpcmelendeztammy@example.org> Delivered-To: melendeztammy@example.org Received: (qmail 62021 invoked from network); 7 May 2006 20:49:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 7 May 2006 20:49:14 -0000 Received: (qmail 68555 invoked by uid 500); 7 May 2006 20:49:14 -0000 Delivered-To: melendeztammy@example.org Received: (qmail 68531 invoked by uid 500); 7 May 2006 20:49:14 -0000 Mailing-List: contact melendeztammy@example.org; run by ezmlm Precedence: bulk list-help: <mailto:melendeztammy@example.org> list-unsubscribe: <mailto:melendeztammy@example.org> List-Post: <mailto:melendeztammy@example.org> Reply-To: melendeztammy@example.org List-Id: <xmlrpc-dev.ws.apache.org> Delivered-To: mailing list melendeztammy@example.org Received: (qmail 68522 invoked by uid 500); 7 May 2006 20:49:14 -0000 Delivered-To: melendeztammy@example.org Received: (qmail 68519 invoked by uid 99); 7 May 2006 20:49:13 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 May 2006 13:49:13 -0700 X-ASF-Spam-Status: No, hits=-9.3 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME,SUBJECT_NOVOWEL X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO minotaur.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with SMTP; Sun, 07 May 2006 13:49:13 -0700 Received: (qmail 61953 invoked by uid 65534); 7 May 2006 20:48:53 -0000 Message-ID: <melendeztammy@example.org> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r404846 - in /webservices/xmlrpc/trunk: client/src/main/java/org/apache/xmlrpc/client/XmlRpcHttpTransport.java client/src/main/java/org/apache/xmlrpc/client/XmlRpcLiteHttpTransport.java src/changes/changes.xml Date: Sun, 07 May 2006 20:48:52 -0000 To: melendeztammy@example.org From: melendeztammy@example.org X-Mailer: svnmailer-1.0.8 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Author: jochen Date: Sun May 7 13:48:51 2006 New Revision: 404846 URL: http://svn.apache.org/viewcvs?rev=404846&view=rev Log: HTTP/1.0 (which is the only version supported by the Lite HTTP transport) requires the presence of a valid content-length header. Consequently, the Lite HTTP transport will from now on reject the contentLengthOptional setting. Modified: webservices/xmlrpc/trunk/client/src/main/java/org/apache/xmlrpc/client/XmlRpcHttpTransport.java webservices/xmlrpc/trunk/client/src/main/java/org/apache/xmlrpc/client/XmlRpcLiteHttpTransport.java webservices/xmlrpc/trunk/src/changes/changes.xml Modified: webservices/xmlrpc/trunk/client/src/main/java/org/apache/xmlrpc/client/XmlRpcHttpTransport.java URL: http://svn.apache.org/viewcvs/webservices/xmlrpc/trunk/client/src/main/java/org/apache/xmlrpc/client/XmlRpcHttpTransport.java?rev=404846&r1=404845&r2=404846&view=diff ============================================================================== --- webservices/xmlrpc/trunk/client/src/main/java/org/apache/xmlrpc/client/XmlRpcHttpTransport.java (original) +++ webservices/xmlrpc/trunk/client/src/main/java/org/apache/xmlrpc/client/XmlRpcHttpTransport.java Sun May 7 13:48:51 2006 @@ -94,8 +94,8 @@ initHttpHeaders(pRequest); return super.sendRequest(pRequest); } - - protected boolean isUsingByteArrayOutput(XmlRpcHttpClientConfig pConfig) { + + protected boolean isUsingByteArrayOutput(XmlRpcHttpClientConfig pConfig) throws XmlRpcException { return !pConfig.isEnabledForExtensions() || !pConfig.isContentLengthOptional(); } Modified: webservices/xmlrpc/trunk/client/src/main/java/org/apache/xmlrpc/client/XmlRpcLiteHttpTransport.java URL: http://svn.apache.org/viewcvs/webservices/xmlrpc/trunk/client/src/main/java/org/apache/xmlrpc/client/XmlRpcLiteHttpTransport.java?rev=404846&r1=404845&r2=404846&view=diff ============================================================================== --- webservices/xmlrpc/trunk/client/src/main/java/org/apache/xmlrpc/client/XmlRpcLiteHttpTransport.java (original) +++ webservices/xmlrpc/trunk/client/src/main/java/org/apache/xmlrpc/client/XmlRpcLiteHttpTransport.java Sun May 7 13:48:51 2006 @@ -231,7 +231,15 @@ } } - protected void writeRequest(RequestWriter pWriter) throws XmlRpcException { + protected boolean isUsingByteArrayOutput(XmlRpcHttpClientConfig pConfig) throws XmlRpcException { + boolean result = super.isUsingByteArrayOutput(pConfig); + if (!result) { + throw new XmlRpcException("The Content-Length header is required with HTTP/1.0, and HTTP/1.1 is unsupported by the Lite HTTP Transport."); + } + return result; + } + + protected void writeRequest(RequestWriter pWriter) throws XmlRpcException { OutputStream ostream = getOutputStream(); pWriter.write(ostream); } Modified: webservices/xmlrpc/trunk/src/changes/changes.xml URL: http://svn.apache.org/viewcvs/webservices/xmlrpc/trunk/src/changes/changes.xml?rev=404846&r1=404845&r2=404846&view=diff ============================================================================== --- webservices/xmlrpc/trunk/src/changes/changes.xml (original) +++ webservices/xmlrpc/trunk/src/changes/changes.xml Sun May 7 13:48:51 2006 @@ -37,6 +37,11 @@ The Base64 encoder doesn't accept buffers of length 0. Such a buffer was passed, if the byte array to encode has itself length 0. </action> + <action dev="jochen" type="fix" issue="XMLRPC-79"> + HTTP/1.0 requires a content-length header. The Lite HTTP transport + doesn't support HTTP/1.1, so it refuses the "contentLengthOptional" + setting from now on. + </action> </release> <release version="3.0a1" date="17-Feb-2005"> <action dev="jochen" type="enhancement"> From xmlrpcmelendeztammy@example.org Sun May 07 20:53:02 2006 Return-Path: <xmlrpcmelendeztammy@example.org> Delivered-To: melendeztammy@example.org Received: (qmail 62645 invoked from network); 7 May 2006 20:53:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 7 May 2006 20:53:02 -0000 Received: (qmail 69559 invoked by uid 500); 7 May 2006 20:53:01 -0000 Delivered-To: melendeztammy@example.org Received: (qmail 69536 invoked by uid 500); 7 May 2006 20:53:01 -0000 Mailing-List: contact melendeztammy@example.org; run by ezmlm Precedence: bulk list-help: <mailto:melendeztammy@example.org> list-unsubscribe: <mailto:melendeztammy@example.org> List-Post: <mailto:melendeztammy@example.org> Reply-To: melendeztammy@example.org List-Id: <xmlrpc-dev.ws.apache.org> Delivered-To: mailing list melendeztammy@example.org Received: (qmail 69527 invoked by uid 99); 7 May 2006 20:53:01 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 May 2006 13:53:01 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 May 2006 13:53:00 -0700 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 93A6A7142C4 for <melendeztammy@example.org>; Sun, 7 May 2006 20:52:21 +0000 (GMT) Message-ID: <24112120.1147035141602.JavaMail.jira@brutus> Date: Sun, 7 May 2006 20:52:21 +0000 (GMT+00:00) From: "Jochen Wiedmann (JIRA)" <melendeztammy@example.org> To: melendeztammy@example.org Subject: [jira] Geschlossen: (XMLRPC-5) We have the problem which is not terminated normally the operation of WebServer service. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/XMLRPC-5?page=all ] Jochen Wiedmann closed XMLRPC-5: -------------------------------- Resolution: Won't Fix Assign To: (was: rpc-dev mailing list) It is quite likely, that this problem no longer applies with versions 2 and 3. Consequently, I am closing the issue now. If required, please reopen. > We have the problem which is not terminated normally the operation of WebServer service. > ---------------------------------------------------------------------------------------- > > Key: XMLRPC-5 > URL: http://issues.apache.org/jira/browse/XMLRPC-5 > Project: XML-RPC > Type: Bug > Components: Source > Versions: unspecified > Environment: Operating System: Windows NT/2K > Platform: PC > Reporter: Kim Hee-Yong > > * XML-RPC for JAVA. > We have the problem which is not terminated normally the operation of WebServer > service.(shutdown method) > This was grasped by the threadpool causing by the reason why the threadpool is > not initialized. > The problem we are about a version 1.0. > We appended WebServer.java file which is modified to the temporary. > Kim Hee-Yong(Nickname : daffodil) > melendeztammy@example.org > 115-9 Nakwon-dong Chuncheon-si Kangwon-do, Republic of Korea > Mirero C&C Coperation. > * modified WebServer.java > public class WebServer > implements Runnable > { > .... > public void run() > { > .... > } > catch (Exception exception) > { > .... > } > finally > { > System.err.println("Closing XML-RPC server socket."); > try > { > serverSocket.close(); > serverSocket = null; > } > catch (IOException ignore) > {} > releaseThreadPool(); > } > } > public void releaseThreadPool() { > Runner r; > try { > while (true) { > r = (Runner)threadpool.pop(); > if (r.thread.isAlive()) r.thread.interrupt > (); > r.thread = null; > } > } catch (EmptyStackException ex) { } > } > .... > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From xmlrpcmelendeztammy@example.org Sun May 07 20:53:03 2006 Return-Path: <xmlrpcmelendeztammy@example.org> Delivered-To: melendeztammy@example.org Received: (qmail 62681 invoked from network); 7 May 2006 20:53:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 7 May 2006 20:53:03 -0000 Received: (qmail 69882 invoked by uid 500); 7 May 2006 20:53:03 -0000 Delivered-To: melendeztammy@example.org Received: (qmail 69719 invoked by uid 500); 7 May 2006 20:53:02 -0000 Mailing-List: contact melendeztammy@example.org; run by ezmlm Precedence: bulk list-help: <mailto:melendeztammy@example.org> list-unsubscribe: <mailto:melendeztammy@example.org> List-Post: <mailto:melendeztammy@example.org> Reply-To: melendeztammy@example.org List-Id: <xmlrpc-dev.ws.apache.org> Delivered-To: mailing list melendeztammy@example.org Received: (qmail 69710 invoked by uid 99); 7 May 2006 20:53:02 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 May 2006 13:53:02 -0700 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=SUBJECT_NOVOWEL X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 May 2006 13:53:01 -0700 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 69AD47142C8 for <melendeztammy@example.org>; Sun, 7 May 2006 20:52:22 +0000 (GMT) Message-ID: <26616853.1147035142429.JavaMail.jira@brutus> Date: Sun, 7 May 2006 20:52:22 +0000 (GMT+00:00) From: "Jochen Wiedmann (JIRA)" <melendeztammy@example.org> To: melendeztammy@example.org Subject: [jira] Geschlossen: (XMLRPC-8) BasicAuthentication bug in XmlRpcClientLite MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/XMLRPC-8?page=all ] Jochen Wiedmann closed XMLRPC-8: -------------------------------- Resolution: Fixed Assign To: (was: rpc-dev mailing list) It is quite likely, that this problem no longer applies with versions 2 and 3. Consequently, I am closing the issue now. If required, please reopen. > BasicAuthentication bug in XmlRpcClientLite > ------------------------------------------- > > Key: XMLRPC-8 > URL: http://issues.apache.org/jira/browse/XMLRPC-8 > Project: XML-RPC > Type: Bug > Components: Source > Versions: unspecified > Environment: Operating System: Windows NT/2K > Platform: PC > Reporter: Robert Purdy > > Setting the setBasicAuthentication(String, String) while using an instance of > XmlRpcClientLite does not set the (lite) local static String auth. Thus when it > doing the sendRequest() in the XmlRpcClientLite, the check for auth always > returns null, and it skips sending the authentication. > I believe this is becuase the setBasicAuthentication method sets the super's > private String auth variable. > I have corrected this problem by removing the local (XmlRpcClientLite) auth > variable, and providing an accessor method in the super (XmlRpcClient) to > access it's private auth setting. Using this method for the auth check in the > lite client then results in the correct functionality. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From xmlrpcmelendeztammy@example.org Sun May 07 20:55:02 2006 Return-Path: <xmlrpcmelendeztammy@example.org> Delivered-To: melendeztammy@example.org Received: (qmail 63144 invoked from network); 7 May 2006 20:55:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 7 May 2006 20:55:02 -0000 Received: (qmail 70530 invoked by uid 500); 7 May 2006 20:55:01 -0000 Delivered-To: melendeztammy@example.org Received: (qmail 70508 invoked by uid 500); 7 May 2006 20:55:01 -0000 Mailing-List: contact melendeztammy@example.org; run by ezmlm Precedence: bulk list-help: <mailto:melendeztammy@example.org> list-unsubscribe: <mailto:melendeztammy@example.org> List-Post: <mailto:melendeztammy@example.org> Reply-To: melendeztammy@example.org List-Id: <xmlrpc-dev.ws.apache.org> Delivered-To: mailing list melendeztammy@example.org Received: (qmail 70498 invoked by uid 99); 7 May 2006 20:55:01 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 May 2006 13:55:01 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 May 2006 13:55:00 -0700 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 98C1F7142C4 for <melendeztammy@example.org>; Sun, 7 May 2006 20:54:21 +0000 (GMT) Message-ID: <19739017.1147035261623.JavaMail.jira@brutus> Date: Sun, 7 May 2006 20:54:21 +0000 (GMT+00:00) From: "Jochen Wiedmann (JIRA)" <melendeztammy@example.org> To: melendeztammy@example.org Subject: [jira] Geschlossen: (XMLRPC-9) Base64 decoder chokes on a whitespace MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/XMLRPC-9?page=all ] Jochen Wiedmann closed XMLRPC-9: -------------------------------- Resolution: Fixed Assign To: (was: rpc-dev mailing list) Version 2 uses the commons-codec. > Base64 decoder chokes on a whitespace > ------------------------------------- > > Key: XMLRPC-9 > URL: http://issues.apache.org/jira/browse/XMLRPC-9 > Project: XML-RPC > Type: Bug > Components: Source > Versions: unspecified > Environment: Operating System: All > Platform: All > Reporter: Vjekoslav Nesek > Attachments: Base64.patch, Base64Test.patch, Base64Test.patch, FAST-Base64-encoder.patch, FIXED-Base64-encoder.patch, WhitespaceBase64Test.java, patch, patch > > base64 decoder in apache xml-rpc can't handle whitespace > (' ', \r, \n, \t) embeded in Base64 data. As a number of > clients split base64 in a multiple lines (example, > python xmlrpclib) this is a serious interoperability issue. > To make things worse apache xmlrpc don't even throw an > exception, instead it incorrectly decodes data. > In order to fix this bug you can use any of number of > correct opensource base64 encoders available on a net. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From xmlrpcmelendeztammy@example.org Sun May 07 20:55:03 2006 Return-Path: <xmlrpcmelendeztammy@example.org> Delivered-To: melendeztammy@example.org Received: (qmail 63179 invoked from network); 7 May 2006 20:55:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 7 May 2006 20:55:03 -0000 Received: (qmail 70712 invoked by uid 500); 7 May 2006 20:55:02 -0000 Delivered-To: melendeztammy@example.org Received: (qmail 70690 invoked by uid 500); 7 May 2006 20:55:02 -0000 Mailing-List: contact melendeztammy@example.org; run by ezmlm Precedence: bulk list-help: <mailto:melendeztammy@example.org> list-unsubscribe: <mailto:melendeztammy@example.org> List-Post: <mailto:melendeztammy@example.org> Reply-To: melendeztammy@example.org List-Id: <xmlrpc-dev.ws.apache.org> Delivered-To: mailing list melendeztammy@example.org Received: (qmail 70681 invoked by uid 99); 7 May 2006 20:55:02 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 May 2006 13:55:02 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 May 2006 13:55:01 -0700 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 0582F7142C6 for <melendeztammy@example.org>; Sun, 7 May 2006 20:54:22 +0000 (GMT) Message-ID: <32350903.1147035262020.JavaMail.jira@brutus> Date: Sun, 7 May 2006 20:54:22 +0000 (GMT+00:00) From: "Jochen Wiedmann (JIRA)" <melendeztammy@example.org> To: melendeztammy@example.org Subject: [jira] Geschlossen: (XMLRPC-13) Unexpected XML parser behavior MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/XMLRPC-13?page=all ] Jochen Wiedmann closed XMLRPC-13: --------------------------------- Resolution: Fixed Assign To: (was: rpc-dev mailing list) It is quite likely, that this problem no longer applies with versions 2 and 3. Consequently, I am closing the issue now. If required, please reopen. > Unexpected XML parser behavior > ------------------------------ > > Key: XMLRPC-13 > URL: http://issues.apache.org/jira/browse/XMLRPC-13 > Project: XML-RPC > Type: Bug > Components: Source > Versions: unspecified > Environment: Operating System: Windows NT/2K > Platform: PC > Reporter: Philippe Maseres > Attachments: Base64.patch, Base64Test.patch > > When bad requests are addressed to the XmlRpcServer, the XML parser produces > strange results. > Case 1 > ------ > The client sends a wellformed XML request which content is not a correct XML- > RPC call. > The parser seems not to detect the error, and the XmlRpcHandler is called back > with data retained from a previous successful invocation (method name). When > this error occurs in the first request processing, the handler is called with a > null reference... This seems to be a bad data state management in the server's > shared workers. > Sample client code : > URL url = new URL(endpoint); > HttpURLConnection http = (HttpURLConnection) url.openConnection(); > http.setRequestMethod("POST"); > http.setDoOutput(true); > PrintWriter pw = new PrintWriter(http.getOutputStream()); > pw.print("<?xml version=\"1.0\" encoding=\"ISO-8859-1\"?>"); > pw.print("<a>hello</a>"); > pw.flush(); > Case 2 > ------ > The client request content is not melendeztammy@example.org. > The parser detects the invalid format, and sends back an XML-RPC fault > reporting the SAX exception. > Sample client code : > URL url = new URL(endpoint); > HttpURLConnection http = (HttpURLConnection) url.openConnection(); > http.setRequestMethod("POST"); > http.setDoOutput(true); > PrintWriter pw = new PrintWriter(http.getOutputStream()); > pw.print("Bye"); > pw.flush(); > I think these two cases should be handled both as a same invalid invocation. > The client seems not to use the XML-RPC protocol, for instance because of a bad > url configuration, and i'm not sure answering an XML-RPC fault is the best way. > I'd prefer the XmlRpcServer to throw a specific java exception, and thus give > the main program (in our case, servlets) a chance to handle the error at the > lower HTTP level. In deed, any IO exception during the XML/XML-RPC parsing > could also be processed this way. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From xmlrpcmelendeztammy@example.org Sun May 07 20:57:02 2006 Return-Path: <xmlrpcmelendeztammy@example.org> Delivered-To: melendeztammy@example.org Received: (qmail 63488 invoked from network); 7 May 2006 20:57:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 7 May 2006 20:57:02 -0000 Received: (qmail 71201 invoked by uid 500); 7 May 2006 20:57:01 -0000 Delivered-To: melendeztammy@example.org Received: (qmail 71175 invoked by uid 500); 7 May 2006 20:57:01 -0000 Mailing-List: contact melendeztammy@example.org; run by ezmlm Precedence: bulk list-help: <mailto:melendeztammy@example.org> list-unsubscribe: <mailto:melendeztammy@example.org> List-Post: <mailto:melendeztammy@example.org> Reply-To: melendeztammy@example.org List-Id: <xmlrpc-dev.ws.apache.org> Delivered-To: mailing list melendeztammy@example.org Received: (qmail 71166 invoked by uid 99); 7 May 2006 20:57:01 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 May 2006 13:57:01 -0700 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=SUBJECT_NOVOWEL X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 May 2006 13:57:00 -0700 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 9B7EF7142C4 for <melendeztammy@example.org>; Sun, 7 May 2006 20:56:21 +0000 (GMT) Message-ID: <26500866.1147035381592.JavaMail.jira@brutus> Date: Sun, 7 May 2006 20:56:21 +0000 (GMT+00:00) From: "Jochen Wiedmann (JIRA)" <melendeztammy@example.org> To: melendeztammy@example.org Subject: [jira] Geschlossen: (XMLRPC-17) Missing an example using org.apache.xmlrpc.applet.SimpleXmlRpcClient MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/XMLRPC-17?page=all ] Jochen Wiedmann closed XMLRPC-17: --------------------------------- Resolution: Won't Fix Assign To: (was: rpc-dev mailing list) It is unlikely, that there is still interest in such an example, as applets are rarely used nowadays. Consequently, I am closing the issue. Please reopen, if required. > Missing an example using org.apache.xmlrpc.applet.SimpleXmlRpcClient > -------------------------------------------------------------------- > > Key: XMLRPC-17 > URL: http://issues.apache.org/jira/browse/XMLRPC-17 > Project: XML-RPC > Type: Bug > Components: Source > Versions: unspecified > Environment: Operating System: Other > Platform: Other > Reporter: Ryan Hoegg > Attachments: XmlRpcEchoApplet.jar, XmlRpcEchoApplet.java, echoapplet.html > > There are examples for creating an XML-RPC server using the WebServer class, and > for synchronous and asynchronous clients using the XmlRpcClient class, but no > example suitable for an applet programmer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From xmlrpcmelendeztammy@example.org Sun May 07 20:59:02 2006 Return-Path: <xmlrpcmelendeztammy@example.org> Delivered-To: melendeztammy@example.org Received: (qmail 65188 invoked from network); 7 May 2006 20:59:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 7 May 2006 20:59:02 -0000 Received: (qmail 75473 invoked by uid 500); 7 May 2006 20:59:01 -0000 Delivered-To: melendeztammy@example.org Received: (qmail 75441 invoked by uid 500); 7 May 2006 20:59:01 -0000 Mailing-List: contact melendeztammy@example.org; run by ezmlm Precedence: bulk list-help: <mailto:melendeztammy@example.org> list-unsubscribe: <mailto:melendeztammy@example.org> List-Post: <mailto:melendeztammy@example.org> Reply-To: melendeztammy@example.org List-Id: <xmlrpc-dev.ws.apache.org> Delivered-To: mailing list melendeztammy@example.org Received: (qmail 75431 invoked by uid 99); 7 May 2006 20:59:01 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 May 2006 13:59:01 -0700 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=SUBJECT_NOVOWEL X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 May 2006 13:59:00 -0700 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 950147142C8 for <melendeztammy@example.org>; Sun, 7 May 2006 20:58:21 +0000 (GMT) Message-ID: <24521573.1147035501607.JavaMail.jira@brutus> Date: Sun, 7 May 2006 20:58:21 +0000 (GMT+00:00) From: "Jochen Wiedmann (JIRA)" <melendeztammy@example.org> To: melendeztammy@example.org Subject: [jira] Geschlossen: (XMLRPC-19) Add SSL session resumption to XmlRpcClientLite MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/XMLRPC-19?page=all ] Jochen Wiedmann closed XMLRPC-19: --------------------------------- Resolution: Won't Fix Assign To: (was: rpc-dev mailing list) The issue has seen no activity in more than three years. Consequently, I am now closing it. Please reopen, if required. > Add SSL session resumption to XmlRpcClientLite > ---------------------------------------------- > > Key: XMLRPC-19 > URL: http://issues.apache.org/jira/browse/XMLRPC-19 > Project: XML-RPC > Type: Bug > Components: Source > Versions: unspecified > Environment: Operating System: All > Platform: Other > Reporter: Ryan Hoegg > Attachments: SecureXmlRpcClientLite.java, XmlRpcClientLite.java, ssl.txt > > Original post on the dev list: > Last January I was inquiring if anyone knew how to perform SSL session > resumption using an XML-RPC client. I did not receive a solution so I finally > went back and addressed the issue. My solution was to copy the XmlRpcClientLite > class and change the init method to use SSL sockets configured for resumption. > Also on Windows we experienced a performance issue where the HTML header was > being prematurely flushed. In my class I write the HTML header and XML content > to a single byte array and do one write to the socket output stream. Attached > is my class. I would appreciate it greatly if this capability was somehow > incorporated into the Apache base-line. Let me know what you think. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From xmlrpcmelendeztammy@example.org Sun May 07 21:01:03 2006 Return-Path: <xmlrpcmelendeztammy@example.org> Delivered-To: melendeztammy@example.org Received: (qmail 65857 invoked from network); 7 May 2006 21:01:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 7 May 2006 21:01:02 -0000 Received: (qmail 77111 invoked by uid 500); 7 May 2006 21:01:02 -0000 Delivered-To: melendeztammy@example.org Received: (qmail 77091 invoked by uid 500); 7 May 2006 21:01:01 -0000 Mailing-List: contact melendeztammy@example.org; run by ezmlm Precedence: bulk list-help: <mailto:melendeztammy@example.org> list-unsubscribe: <mailto:melendeztammy@example.org> List-Post: <mailto:melendeztammy@example.org> Reply-To: melendeztammy@example.org List-Id: <xmlrpc-dev.ws.apache.org> Delivered-To: mailing list melendeztammy@example.org Received: (qmail 77082 invoked by uid 99); 7 May 2006 21:01:01 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 May 2006 14:01:01 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 May 2006 14:01:01 -0700 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id CE7CC7142C6 for <melendeztammy@example.org>; Sun, 7 May 2006 21:00:21 +0000 (GMT) Message-ID: <1180184.1147035621843.JavaMail.jira@brutus> Date: Sun, 7 May 2006 21:00:21 +0000 (GMT+00:00) From: "Jochen Wiedmann (JIRA)" <melendeztammy@example.org> To: melendeztammy@example.org Subject: [jira] Geschlossen: (XMLRPC-21) de/serialization independence MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/XMLRPC-21?page=all ] Jochen Wiedmann closed XMLRPC-21: --------------------------------- Resolution: Fixed Assign To: (was: rpc-dev mailing list) The XML handling has been completely reworked in version 3. > de/serialization independence > ----------------------------- > > Key: XMLRPC-21 > URL: http://issues.apache.org/jira/browse/XMLRPC-21 > Project: XML-RPC > Type: Bug > Components: Source > Versions: unspecified > Environment: Operating System: Other > Platform: Other > Reporter: Reed Esau > > For serialization (object->XML) can XmlWriter be made public? > For deserialization (XML->object) can the ContentHandler be separated from > XmlRpc, allowing it to be used as an independent SAX handler, with no thread or > SaxDriver discovery code inside? Support for SAX2 DefaultHandler would be nice > too, but not critical. > Use case: where XML-RPC is being used with an alternative transport (JXTA > pipes, e.g.) this separation would allow for much cleaner client > implementations, where these modules can be used for preparing requests and > parsing responses. > Much appreciated! > Reed Esau, melendeztammy@example.org > http://xmlrpc.jxta.org -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From xmlrpcmelendeztammy@example.org Sun May 07 21:01:03 2006 Return-Path: <xmlrpcmelendeztammy@example.org> Delivered-To: melendeztammy@example.org Received: (qmail 65881 invoked from network); 7 May 2006 21:01:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 7 May 2006 21:01:03 -0000 Received: (qmail 77401 invoked by uid 500); 7 May 2006 21:01:03 -0000 Delivered-To: melendeztammy@example.org Received: (qmail 77284 invoked by uid 500); 7 May 2006 21:01:02 -0000 Mailing-List: contact melendeztammy@example.org; run by ezmlm Precedence: bulk list-help: <mailto:melendeztammy@example.org> list-unsubscribe: <mailto:melendeztammy@example.org> List-Post: <mailto:melendeztammy@example.org> Reply-To: melendeztammy@example.org List-Id: <xmlrpc-dev.ws.apache.org> Delivered-To: mailing list melendeztammy@example.org Received: (qmail 77264 invoked by uid 99); 7 May 2006 21:01:02 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 May 2006 14:01:02 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 May 2006 14:01:01 -0700 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 9F2E97142C4 for <melendeztammy@example.org>; Sun, 7 May 2006 21:00:22 +0000 (GMT) Message-ID: <12810883.1147035622649.JavaMail.jira@brutus> Date: Sun, 7 May 2006 21:00:22 +0000 (GMT+00:00) From: "Jochen Wiedmann (JIRA)" <melendeztammy@example.org> To: melendeztammy@example.org Subject: [jira] Geschlossen: (XMLRPC-22) APACHE XMLRPC HTTP header EBCDIC problem OS390 zOS MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/XMLRPC-22?page=3Dall ] =20 Jochen Wiedmann closed XMLRPC-22: --------------------------------- Resolution: Won't Fix Assign To: (was: rpc-dev mailing list) The issue has seen no activity in more than three years. Consequently, I am= now closing it. Please reopen, if required. > APACHE XMLRPC HTTP header EBCDIC problem OS390 zOS > -------------------------------------------------- > > Key: XMLRPC-22 > URL: http://issues.apache.org/jira/browse/XMLRPC-22 > Project: XML-RPC > Type: Bug > Components: Source > Versions: unspecified > Environment: Operating System: Other > Platform: Other > Reporter: jean-yves mulvet > > A java servlet, powered by IBM WEBSPHERE running in the Unix Services (US= S) of=20 > an IBM MVS OS390 or zOS platform, uses the XmlRpcClientLite class from th= e=20 > org.apache.xmlrpc package.=20 > The problem is that the client connection to the server fails. > It doesn't occur with IBM WEBSPHERE running on microsoft NT or WINDOWS 20= 00. > The IPTRACE obtained from the client side shows the following data in DUM= P=20 > format : > Offset Hexadecimal * EBCDIC | ASCII = * > * translation | translation = * > 0000 D7D6E2E3 4061D9D7 C3F240C8 E3E3D761 *POST /RPC2 HTTP/|....=C3=A0a...= .=C3=A0....a* > 0010 F14BF00D 15E4A285 9960C187 8595A37A *1.0..User-Agent:|.K.......=C2= =B5.....z* > 0020 40C19781 83888540 E7D4D360 D9D7C340 * Apache XML-RPC |=C3=A0......= =C3=A0...=C2=B5...=C3=A0* > 0030 F14BF00D 15C896A2 A37A40F1 F04BF2F3 *1.0..Host: 10.23|.K.......z=C3= =A0..K..* > 0040 F04BF9F2 4BF3F97A F8F0F00D 15C39695 *0.92.39:800..Con|.K..K..z......= ..* > 0050 A38595A3 60E3A897 857A40A3 85A7A361 *tent-Type: text/|....=C2=B5....= z=C3=A0....a* > 0060 A794930D 15C39695 A38595A3 60D38595 *xml..Content-Len|............= =C2=B5...* > 0070 87A3887A 40F2F1F1 0D150D15 3C3F786D *gth: 211......._|...z=C3=A0....= ...<?xm* > 0080 6C207665 7273696F 6E3D2231 2E302220 *%......?>.......|l version=3D"1= .0" * > 0090 656E636F 64696E67 3D224953 4F2D3838 *.>.?..>.....|...|encoding=3D"IS= O-88* > 00A0 35392D31 223F3E3C 6D657468 6F644361 *........_...?../|59-1"?><method= Ca* > 00B0 6C6C3E3C 6D657468 6F644E61 6D653E43 *%%.._...?.+/_...|ll><methodName= >C* > 00C0 6F6E6E65 63745573 65723C2F 6D657468 *?>>........._...|onnectUser</me= th* > 00D0 6F644E61 6D653E3C 70617261 6D733E3C *?.+/_...././_...|odName><params= ><* > 00E0 70617261 6D3E3C76 616C7565 3E61646D *././_.../%.../._|param><value>a= dm* > 00F0 696E3C2F 76616C75 653E3C2F 70617261 *.>.../%.....././|in</value></pa= ra* > 0100 6D3E3C70 6172616D 3E3C7661 6C75653E *_..././_.../%...|m><param><valu= e>* > 0110 3C626173 6536343E 59575274 61573471 *../........./...|<base64>YWRtaW= 4q* > 0120 3C2F6261 73653634 3E3C2F76 616C7565 *.../......../%..|</base64></val= ue* > 0130 3E3C2F70 6172616D 3E3C2F70 6172616D *...././_...././_|></param></par= am* > 0140 733E3C2F 6D657468 6F644361 6C6C3ED7 *...._...?../%%.P|s></methodCall= >.* > We can see the HTTP header is coded in EBCDIC > This doesn't comply with the RFC which says HTTP header must be US-ASCII = coded. > So, the HTTP XMLRPC server is unable to understand the data received and = close=20 > the connection. > It seems the problem arises in the following section of apache code, beca= use=20 > native encoding of an MVS OS390 or zOS platform is EBCDIC : > http://xml.apache.org/xmlrpc/xref/org/apache/xmlrpc/XmlRpcClientLite > package org.apache.xmlrpc; > public InputStream sendRequest (byte[] request) throws IOException > { > output.write (("POST "+uri + " HTTP/1.0\r\n").getBytes()); > output.write ( ("User-Agent: "+XmlRpc.version + "\r\n").getBytes()); > output.write (("Host: "+host + "\r\n").getBytes()); > if (XmlRpc.getKeepAlive()) > output.write ("Connection: Keep-Alive\r\n".getBytes ()); > output.write ("Content-Type: text/xml\r\n".getBytes ()); > if (auth !=3D null) > output.write ( ("Authorization: Basic "+auth + "\r\n").getBytes()); > output.write ( ("Content-Length: "+request.length).getBytes ()); > output.write ("\r\n\r\n".getBytes()); > output.write (request); > output.flush (); > ....... > So, we tried the following modified code : > =20 > public InputStream sendRequest (byte[] request) throws IOException > { > output.write (("POST "+uri + " HTTP/1.0\r\n").getBytes(XmlRpc.encoding= )); > output.write ( ("User-Agent: "+XmlRpc.version + "\r\n").getBytes > (XmlRpc.encoding)); > output.write (("Host: "+host + "\r\n").getBytes(XmlRpc.encoding)); > if (XmlRpc.getKeepAlive()) > output.write ("Connection: Keep-Alive\r\n".getBytes (XmlRpc.encodin= g)); > output.write ("Content-Type: text/xml\r\n".getBytes (XmlRpc.encodin= g)); > if (auth !=3D null) > output.write ( ("Authorization: Basic "+auth + "\r\n").getBytes > (XmlRpc.encoding)); > output.write ( ("Content-Length: "+request.length).getBytes=20 > (XmlRpc.encoding)); > output.write ("\r\n\r\n".getBytes(XmlRpc.encoding)); > output.write (request); > output.flush (); > ....... > The IP trace made after the modification shows that the problem is bypass= ed : > HTTP header is now US-ASCII coded. > Offset Hexadecimal *
{'source': 'Apache Software Foundation Public Mail Archives'}