Re: Using ERRest but with extensions for non EOF back-end
Re: Using ERRest but with extensions for non EOF back-end
- Subject: Re: Using ERRest but with extensions for non EOF back-end
- From: "Brook, James" <email@hidden>
- Date: Fri, 15 Jan 2010 12:18:05 +0100
- Acceptlanguage: en-US
- Thread-topic: Using ERRest but with extensions for non EOF back-end
The existing API uses the entity delegate API.
On 14 Jan 2010, at 17:38, Mike Schrag wrote:
> are you use the entity delegate api or the route controller api?
>
> On Jan 14, 2010, at 11:36 AM, Brook, James wrote:
>
>> We have a WebObjects application that uses the ERRest framework to
>> provide a RESTful API over our EOModel. We now want to extend the API
>> to cover some other legacy back-office services and persistence
>> mechanisms as well. The plan is to use fairly plain Java objects and
>> perhaps key value coding. Is there a straightforward path to support
>> this, while making the RESTful API look seamless across the EOF and
>> the alternative back-end logic? I am concerned that we might have to
>> make lots of adaptations to support this model.
>>
>> Any tips would be very much appreciated.
>>
>> --
>> James
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden