• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Using ERRest but with extensions for non EOF back-end
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using ERRest but with extensions for non EOF back-end


  • Subject: Re: Using ERRest but with extensions for non EOF back-end
  • From: Mike Schrag <email@hidden>
  • Date: Fri, 15 Jan 2010 07:19:41 -0500

Pretty sure you can't do this ... I think the entity delegate stuff is entirely EOEntity-baed. When I made the newer route controller approach, support for non-entity objects was part of the requirements for it. I started to backport it to the entity delegates, but it was just too big of a change for an API and it would have caused problems with the D2Rest code, which requires entities. You COULD choose to mix the entity delegates and newer stuff, i think ... So you don't have to throw away the code you've already written for the entity delegates.

ms

On Jan 15, 2010, at 6:18 AM, Brook, James wrote:

> 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

  • Follow-Ups:
    • Re: Using ERRest but with extensions for non EOF back-end
      • From: "Brook, James" <email@hidden>
References: 
 >Using ERRest but with extensions for non EOF back-end (From: "Brook, James" <email@hidden>)
 >Re: Using ERRest but with extensions for non EOF back-end (From: Mike Schrag <email@hidden>)
 >Re: Using ERRest but with extensions for non EOF back-end (From: "Brook, James" <email@hidden>)

  • Prev by Date: Re: WO Long Response and iPhone
  • Next by Date: Re: D2WS Assistant
  • Previous by thread: Re: Using ERRest but with extensions for non EOF back-end
  • Next by thread: Re: Using ERRest but with extensions for non EOF back-end
  • Index(es):
    • Date
    • Thread