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 vasunori@gmail.com designates
 66.249.82.225 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:references;
        b=AvPygm+a0y4oKzv2AuaYKSPt77KvlH2Wtnr13hXE5Bn/M4lksnjwtbBcbbCdHyxaZpen3qsLz1njjhB0WS5leLpnGV1xSuYbHC1cEE8GY6BxPDitYFwSnsqtgFZ9CDXy/K0cql3Z9Ye4uaaEY+KPk713uscAjRyQp/A1S7KcDf8=
Message-ID: <41a5ab360802050937x32287dd6n3532a61f142a0231@mail.gmail.com>
Date: Tue, 5 Feb 2008 09:37:48 -0800
From: "Vasu Nori" <vasunori@gmail.com>
To: abdera-user@incubator.apache.org
Subject: Re: REST services along side Atom APP
In-Reply-To: <47A7C5A4.8050005@mulesource.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_20019_5309809.1202233068160"
References: <9265C9D84FEE41FA8D5D8D4BC98F63EB@ArrovaL001>
	 <47A7C5A4.8050005@mulesource.com>

------=_Part_20019_5309809.1202233068160
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Feb 4, 2008 6:10 PM, Dan Diephouse <dan.diephouse@mulesource.com> wrote:

> You should be able to extend the Provider/Resolver APIs enough inside
> abdera to handle this type of thing. For instance, if you wanted to
> override the PUT handling, you would just detect that inside
> CollectionAdapter.putEntry().
>
> On a related note, I've looked at integrating say Restlet and Abdera. Or
> JAX-RS and Abdera. They're complimentary IMO. For instance once could
> theoretically use a Restlet router to direct requests to Abdera or a
> Restlet. One would just need to create a restlet Request -> Abdera
> RequestContext mapping.
>

this sounds great. I haven't had time to play with it yet.
but if anyone does build it this way, please share it - or better yet, chec=
k
it into examples/ dir in abdera repo.


> Cheers,
> - Dan
>
> Remy Gendron wrote:
> > Hello all,
> >
> >
> >
> > Has anybody given thoughts on how to implement standard REST services o=
n
> top
> > of Atom/APP/Abdera.
> >
> >
> >
> > For instance:
> >
> >
> >
> > Assume I have entity A which is subject to a workflow process in my
> business
> > layer.
> >
> >
> >
> > Of course, CRUDs are implemented as APP/Abdera interactions.
> >
> >
> >
> > But how would I go about triggering a workflow action on A and getting
> back
> > the new workflow state of A?
> >
> >
> >
> > Should I do an APP PUT on the targeted entry with additional parameters
> > associated to the workflow action and alter my PUT handling in the
> adapter
> > when I detect those parameters?
> >
> >
> >
> > Should I create dedicated standard REST calls to handle these actions
> > outside of the APP universe? Is Atom/APP exclusively reserved to CRUD
> > syndication?
> >
> >
> >
> > If the latter is recommended, I will alter my server configuration so
> that
> > the Abdera servlet only services calls to
> > //domain/appctx/feeds/collection_id/entry_id. Currently, the Abdera
> servlet
> > handles everything under the application context. I would now use
> > //domain/appctx/rest/=85 for everything not APP.
> >
> >
> >
> > Your thoughts?
> >
> >
> >
> > R=E9my
> >
> >
> > No virus found in this outgoing message.
> > Checked by AVG Free Edition.
> > Version: 7.5.516 / Virus Database: 269.19.19/1258 - Release Date:
> 2008.02.04
> > 10:10
> >
> >
> >
>
>
> --
> Dan Diephouse
> MuleSource
> http://mulesource.com | http://netzooid.com/blog
>
>

------=_Part_20019_5309809.1202233068160--