Mailing-List: contact avro-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: avro-user@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of gmporter@gmail.com designates
 209.85.216.171 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=eC6rvL1mlGMTsgA2IC8Vgr9F0DLkogvQhexRtpE/0dAdgU3ZLy1vy9jfxbRYH87mtg
         dPHw+XkJSUGaBfQb2w7qF3y9wz8b32lNNrXYqqDz5khs/VfqzsMpDAGS2OKHT02yOEJd
         e1FZuwmc9ClPjm8FhkUVT46yka2so76xrZGsU=
MIME-Version: 1.0
In-Reply-To: <4A73843F.6030207@apache.org>
References: <cd40e6450907311454ifa94d12tacde64e6b342989c@mail.gmail.com>
	 <4A73843F.6030207@apache.org>
Date: Fri, 31 Jul 2009 17:05:52 -0700
Message-ID: <cd40e6450907311705t3118a97an9a2dece16293aea4@mail.gmail.com>
Subject: Re: How to define an RPC message with a void return type
From: George Porter <gmporter@gmail.com>
To: avro-user@hadoop.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

The issue showed up when I was implementing put() on the server side.

I had written the method like this:

{code}
@Override
  public Void put(ByteBuffer key, ByteBuffer value) throws AvroRemoteExcept=
ion {
    kvstore.put(key, value);
  }
{code}

and was getting compiler errors.  I just added a "return null;" and it
fixed the problem.  I guess that I had expected the compiler to
produce a method with a return type of 'void', rather than 'Void'.

Thanks,
George

On Fri, Jul 31, 2009 at 4:54 PM, Doug Cutting<cutting@apache.org> wrote:
> George Porter wrote:
>>
>> The 'put' message gets compiled into the following signature in Java:
>>
>> {code}
>> Void put(ByteBuffer key, ByteBuffer value)
>> =A0 =A0throws AvroRemoteException;
>> {code}
>>
>> Unfortunately, Void isn't an instantiatable type in Java. =A0Any thought=
s?
>
> When do you need to instantiate a Void? =A0I'm not saying this isn't a
> problem, I'm just not yet sure where the problem is.
>
> Doug
>