From dev-return-5399-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Wed Apr 20 17:03:31 2005 Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 19623 invoked from network); 20 Apr 2005 17:03:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 20 Apr 2005 17:03:31 -0000 Received: (qmail 24819 invoked by uid 500); 20 Apr 2005 08:03:36 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 24771 invoked by uid 500); 20 Apr 2005 08:03:35 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 24734 invoked by uid 99); 20 Apr 2005 08:03:35 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of trustin@gmail.com designates 64.233.184.192 as permitted sender) Received: from wproxy.gmail.com (HELO wproxy.gmail.com) (64.233.184.192) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 20 Apr 2005 01:03:35 -0700 Received: by wproxy.gmail.com with SMTP id 70so89226wra for ; Wed, 20 Apr 2005 01:03:33 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=cY7xN+8oD4G7CE936HAODfnGxBAIe0L1F7N8VoCFLGDkJaKyC0HYU3LWk5yxBj74uLB28tvi44HaFlTuS8/ua+F+FioBb84twJi/B5OlvyS3e2UeYhnrfLyziDnX5xdq49UHjIFDS8i/J4GbPBZvWdZ+mC/FvRhh52PniZzRdRo= Received: by 10.54.50.13 with SMTP id x13mr18837wrx; Wed, 20 Apr 2005 01:03:33 -0700 (PDT) Received: by 10.54.70.20 with HTTP; Wed, 20 Apr 2005 01:03:33 -0700 (PDT) Message-ID: <768dcb2e05042001037dce3c03@mail.gmail.com> Date: Wed, 20 Apr 2005 17:03:33 +0900 From: Trustin Lee Reply-To: Trustin Lee To: Apache Directory Developers List , Vinod Panicker Subject: Re: [mina] ByteBuffer problem? In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi Vinod, 2005/4/20, Vinod Panicker : > Hi Trustin, >=20 > Here's the code that I was having a problem with - >=20 > -- begin code -- >=20 > public void decode(ProtocolSession session, ByteBuffer in, > ProtocolDecoderOutput out) > { > ByteBuffer temp =3D ByteBuffer.allocate(in.capacity()); > temp.put(in); > temp.flip().limit(in.limit()); > in.flip(); > System.out.println("[D] Data decoded : " + in.getHexDump()); > System.out.println("[D] Data decoded char : " + in.getString(in.li= mit(), > Charset.defaultCharset().newDecoder())); > out.write(temp); > } There was a bug in getString() methods. SVN server is down for now.=20 I'll check in the fix and test cases soon. I'm sorry for inconvenience! Trustin --=20 what we call human nature is actually human habit -- http://gleamynode.net/