[ http://issues.apache.org/jira/browse/JCR-544?page=comments#action_12434477 ] angela commented on JCR-544: ----------------------------
additional thoughts: what is actually missing in the jcr-server is a distint resource representing the 'workspace'. currently the root node also acts somehow as workspace. i will take a closer look at this point, which may provide also a smarter solution for this bug. > JCR-Server: Workspace.restore not mapped correctly > -------------------------------------------------- > > Key: JCR-544 > URL: http://issues.apache.org/jira/browse/JCR-544 > Project: Jackrabbit > Issue Type: Bug > Reporter: angela > Assigned To: angela > > (issue reported by David Kennedy) > Workspace.restore(Version[], boolean) won't work, since versions are not > retrieved correctly. The version history that can be access from the request > resource, cannot be used to retrieve the versions needed for a > workspace.restore call. > possible short term fix: > From the version-hrefs present in the request body of the UPDATE request, > version resources must be built and > the corresponding version item retrieved. > alternative: > find a proper mapping for Workspace.restore(Version[], boolean). having > UPDATE on a resource representing a javax.jcr.Node being mapped to a > workspace.restore is odd. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
