Return-Path: 
 <abdera-dev-return-1845-apmail-incubator-abdera-dev-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-abdera-dev-archive@locus.apache.org
Received: (qmail 41556 invoked from network); 9 Jan 2008 18:38:49 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 9 Jan 2008 18:38:49 -0000
Received: (qmail 33531 invoked by uid 500); 9 Jan 2008 18:38:37 -0000
Delivered-To: apmail-incubator-abdera-dev-archive@incubator.apache.org
Received: (qmail 33508 invoked by uid 500); 9 Jan 2008 18:38:37 -0000
Mailing-List: contact abdera-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:abdera-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:abdera-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:abdera-dev@incubator.apache.org>
List-Id: <abdera-dev.incubator.apache.org>
Reply-To: abdera-dev@incubator.apache.org
Delivered-To: mailing list abdera-dev@incubator.apache.org
Received: (qmail 33498 invoked by uid 99); 9 Jan 2008 18:38:37 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Jan 2008 10:38:37 -0800
X-ASF-Spam-Status: No, hits=1.2 required=10.0
	tests=SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Received: from [66.111.4.29] (HELO out5.smtp.messagingengine.com)
 (66.111.4.29)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Jan 2008 18:38:25 +0000
Received: from compute1.internal (compute1.internal [10.202.2.41])
	by out1.messagingengine.com (Postfix) with ESMTP id 3C8D186FD6
	for <abdera-dev@incubator.apache.org>; Wed,  9 Jan 2008 13:38:17 -0500 (EST)
Received: from heartbeat1.messagingengine.com ([10.202.2.160])
  by compute1.internal (MEProxy); Wed, 09 Jan 2008 13:38:17 -0500
X-Sasl-enc: Huf8nnEPBciTy1h/80+fa1wlv3K9T7KM+Ad1EfLcd8Pr 1199903897
Received: from [10.10.2.18] (unknown [38.97.74.254])
	by mail.messagingengine.com (Postfix) with ESMTP id 0C884C771
	for <abdera-dev@incubator.apache.org>; Wed,  9 Jan 2008 13:38:17 -0500 (EST)
Message-ID: <47851497.8080805@anconafamily.com>
Date: Wed, 09 Jan 2008 13:38:15 -0500
From: Jim Ancona <jim@anconafamily.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: abdera-dev@incubator.apache.org
Subject: Re: Making a Provider a Resolver
References: <47840A2D.2090909@mulesource.com>
In-Reply-To: <47840A2D.2090909@mulesource.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Dan Diephouse wrote:
> I was wondering: does anyone see a clean way to auto-detect that a 
> Provider also implements Resolver and use it automatically instead of 
> having the user specify both?

How about if ServiceProvider implemented ItemManager<Provider> in 
addition to Provider (i.e. acted as its own Manager)? The ServiceContext 
could then use reflection to detect that one object implements both 
Resolver<Target> and ItemManager<Provider> and use it for both purposes.

Jim