On Thu, Feb 20, 2014 at 6:37 AM, Stanton Sievers <[email protected]>wrote:
> Hi all, > > I've been working a lot with the page cloning functionality in Rave > recently (you might have noticed). I've discovered a need to move the > clone API to CXF so that the Page object returned from the clone page API > matches the page object structure expected by API calls like updatePage > which is currently implemented via CXF. > > I've done some investigating and I have some questions I'm hoping this list > could help answer. I've noticed that org.apache.rave.rest.PagesResource > doesn't have a clone API currently. It used to have one but was removed > with commit 1505802 with a comment of " update to Resource interfaces to > support proposed api specification". I'm wondering why the clone API was > removed from PagesResource. Did it move somewhere else? Can anyone > elaborate on the mentioned "api specification". > http://wiki.apache.org/rave/RESTAPI There were also a bunch of e-mail threads around the proper way to approach this. If I remember right, there were some proponents for making clone a combination of a GET and a POST of the page to the API. I think there are some nuances in cloning that this might not cover though. > > I noticed that RAVE-924 [1] has been resolved and I don't see any other > page related tasks in its parent, RAVE-910 [2]. > > [1] https://issues.apache.org/jira/browse/RAVE-924 > [2] https://issues.apache.org/jira/browse/RAVE-910 We can add a new ticket to the parent if client side copying does not accomplish what we need to do. > > > Thanks, > -Stanton >
