[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ecf-dev] Async-Methods
- From: Wim Jongman <wim.jongman@xxxxxxxxx>
- Date: Mon, 22 Nov 2010 14:09:25 +0100
- Delivered-to: email@example.com
- 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; b=N1ScIhs50NkGx/nSCV1HSXS1Ylo2lizx4wBTu7EWCGc/qYBBP524Msjo4h788EEUvQ wMItmyx6UbPCK7zk93sFHnywwK02I/sKACMbW7e3LlFZXDbZXnhfgF1mR+dVzhYWL2L2 CiChc5TzdjEJrZSNY2KadlvVp1VE6fsYKKvS8=
Ah, thanks! But we do get two service registrations for the same object right?
On Mon, Nov 22, 2010 at 1:36 PM, Markus Alexander Kuppe <firstname.lastname@example.org>
Technically it's not a second service instance that gets registered. It
On 11/22/2010 01:22 PM, Wim Jongman wrote:
> No need to register the service with async.
> When ECF registers a remote service it will detect if a class with the
> name ...Async is found in the classpath. It will then register this
> service automatically alongside the normal service. So ECF does the
> registration for you, you only need to pick it up from the service registry.
is in fact the same service proxy instance on the client side that
happens to implement both interfaces. The original as well as the *Async