Mailing-List: contact abdera-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: abdera-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of david.primmer@gmail.com
 designates 209.85.146.181 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=N6osGYSpiKxU6OaEnzUPMgRovsuAna/u9b6NbMASiLus5Klq5BaFzoxLHKUdYwRf1jLjEaxPg2G25SQbZ0nYa8s2HIPN7FGCQ75+i34Z4CClwrjqh9ChtImRc1eRQEKCYTOog1E47g8DCDwq6z4huMyA1Lg42aYm6SuvJCe6U9s=
Message-ID: <ce54216b0804152054l4dcd3848r875d3723f818316@mail.gmail.com>
Date: Tue, 15 Apr 2008 20:54:51 -0700
From: "David Primmer" <david.primmer@gmail.com>
To: abdera-user@incubator.apache.org
Subject: Re: CustomProvider example not intended to host more than one
 adapter?
In-Reply-To: <48056B3E.8070709@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <ce54216b0804151835x1c2eb98bp6bd4a00ff48efb0@mail.gmail.com>
	 <48056B3E.8070709@gmail.com>

There is something very similar to this in RouteManager.resolve but it
returns a target object and not a CA. I suppose i can just lift that
code. Now I understand why it still finds the CA when the last
collectionadapter argument was left off in the DefaultProvider's route
specifications. Thanks.

davep

On Tue, Apr 15, 2008 at 7:58 PM, James M Snell <jasnell@gmail.com> wrote:
> The CustomProvider example only supports a single adapter but the
> AbstractWorkspaceProvider can provide as many as necessary by overriding the
> getCollectionAdapter(RequestContext) method.  I have a current
> implementation using a subclass of AWP that returns one of five different
> adapters depending on the Target type.
>
>  - James
>
>
>
>  David Primmer wrote:
>
> > I've swapped out routing in the CustomProvider and I'm trying to use
> > multiple adapters. CP extends AbstractWorkspaceProvider. That
> > implements WorkspaceManager which requires you to implement
> > getCollectionAdapter(RequestContext request) in your provider; This is
> > easy if you just use one adapter in this provider, you just return it
> > as the sample shows. However, what if you have a number of workspaces
> > and adapters. AbstractWorkspaceProvider looks like it should support
> > this.
> >
> > Since I'm using RouteManager I thought the RouteManager.resolve would
> > handle this dispatching.  Should I abandon CP for DefaultProvider?
> >
> > thanks again!
> >
> > davep
> >
> >
>