Mailing-List: contact river-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: river-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4B713FA5.7090808@zeus.net.au>
Date: Tue, 09 Feb 2010 20:57:41 +1000
From: Peter Firmstone <jini@zeus.net.au>
Organization: Zeus Project Services
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: river-dev@incubator.apache.org
Subject: Re: Service Wrapper Example
References: <c5dcc791002090221k4876a8e8jaa38c31bb1cf9fb0@mail.gmail.com>
In-Reply-To: <c5dcc791002090221k4876a8e8jaa38c31bb1cf9fb0@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hey, thanks Tom, there's still some life in River yet old mate, off to 
bed now so I'll have a look in the morning.

Cheers,

Peter.

Tom Hobbs wrote:
> Hi,
>
> I mentioned in another thread that I had come across code which provides
> service fail over and auto-rediscovery.  I've posted details of the kind of
> code that was used to (note this has been reinvented in my head just now and
> only loosely tested);
>
> http://wiki.apache.org/river/AutomaticServiceReplacement
>
> I hope that someone finds it useful and/or interesting.
>
> It's important to note that in the interests of simplicity the
> ServiceWrapper class in the article is explicitly linked to the dummy
> service described.  Obviously using more reflection magic it's possible to
> remove this linkage so that ServiceWrapper can wrap any service you like and
> it's invoke method would invoke the method supplied to it, rather than the
> only method available in the dummy article.
>
> Thanks to Jukka for his Wiki account suggestion.
>
> Enjoy,
>
> Tom
>
>