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 protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
