Return-Path: Delivered-To: apmail-jakarta-httpclient-user-archive@www.apache.org Received: (qmail 13250 invoked from network); 29 Jun 2006 17:42:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 29 Jun 2006 17:42:53 -0000 Received: (qmail 28168 invoked by uid 500); 29 Jun 2006 17:42:53 -0000 Delivered-To: apmail-jakarta-httpclient-user-archive@jakarta.apache.org Received: (qmail 28153 invoked by uid 500); 29 Jun 2006 17:42:52 -0000 Mailing-List: contact httpclient-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: "HttpClient User Discussion" Reply-To: "HttpClient User Discussion" Delivered-To: mailing list httpclient-user@jakarta.apache.org Received: (qmail 28141 invoked by uid 99); 29 Jun 2006 17:42:52 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Jun 2006 10:42:52 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [212.227.126.187] (HELO moutng.kundenserver.de) (212.227.126.187) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Jun 2006 10:42:52 -0700 Received: from [85.180.12.205] (helo=[85.180.12.205]) by mrelayeu.kundenserver.de (node=mrelayeu2) with ESMTP (Nemesis), id 0MKwtQ-1Fw0X82CXd-0001RV; Thu, 29 Jun 2006 19:42:30 +0200 Message-ID: <44A4117A.9000205@dubioso.net> Date: Thu, 29 Jun 2006 19:44:26 +0200 From: Roland Weber User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.13) Gecko/20060428 X-Accept-Language: en-us, en MIME-Version: 1.0 To: HttpClient User Discussion Subject: Re: Invalid stream header References: <1c0978740606290853s7d4c866fp6ab3c628e84b43c6@mail.gmail.com> <44A404F0.7010502@dubioso.net> <1c0978740606291034w57bfdf58g6ed45abcbba1d45e@mail.gmail.com> In-Reply-To: <1c0978740606291034w57bfdf58g6ed45abcbba1d45e@mail.gmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Provags-ID: kundenserver.de abuse@kundenserver.de login:4601b1d39ab4ddfc21c613822e406392 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi sANTo, > With the default sun classes I wrote everything to an ObjectOutputStream, > but I couldn't find a similar > approach for HttpClient. That's just the kind of question to ask on this list :-) > If I understand it correctly what you are saying, then I should look at > entities, which > allow me to do the same as I did before with the default sun classes. Yes, exactly. Implementing the RequestEntity interface is the way to go. You'll get an OutputStream, on top of which you can put your ObjectOutputStream to write the message body. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: httpclient-user-help@jakarta.apache.org