Mailing-List: contact abdera-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: abdera-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of ixjonez@gmail.com designates
 209.85.146.181 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=dY4+mpmutER8m/o/FcwoLPqMFZmzvR11GU9rexoNL32INYrtYJS9T4288wpGYFJ/8X7H3mLfpPn8T5qgqXCKR+khjPgHSCIYAjiE8f2TTSGge8q+afc4FcB3lfhzuHUdXgL4TOg0/2c4nR8BV7nj2DP9v/lvgJbXLCi++9HRLRI=
Message-ID: <29a761a00709110725na2579f8q2d0967c13b1464d0@mail.gmail.com>
Date: Tue, 11 Sep 2007 07:25:49 -0700
From: "Brian Moseley" <bcm@osafoundation.org>
Sender: ixjonez@gmail.com
To: abdera-dev@incubator.apache.org
Subject: Re: Resolvers and Providers and URLs
In-Reply-To: <46E6178F.6020009@mulesource.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <46E6178F.6020009@mulesource.com>

On 9/10/07, Dan Diephouse <dan.diephouse@mulesource.com> wrote:

> How are other people handling this? Are people hard coding their URL
> strucutre into the actual Provider? Does any one have any ideas on how
> to better integrate the two concepts so that I need to need to let both
> my resolver and my provider know about the URL structure?

i have a helper class that knows about the url structure and is used
by both the target resolver and the provider.

one sort of blue sky idea is to annotate each provider method with a
url pattern and then have abdera process those annotations and build a
mapping of method+provider to url pattern that can be used by a
generic target resolver. this sort of re-casts the provider as a
per-resource helper object, which is how i've wound up using it
anyway.