jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-544) JCR-Server: Workspace.restore not mapped correctly
Date Wed, 20 Sep 2006 16:46:23 GMT
    [ http://issues.apache.org/jira/browse/JCR-544?page=comments#action_12436275 ] 
angela commented on JCR-544:

rev. 448257:

- introduces a distinct resource for the workspace, that does not represent the root-node
at the same time
- Workspace.restore is now handled by this resource.

since this implied some additional changes (e.g. defining a fake name for the resource representing
 the root node)
i will perform some more tests, before resolving this issue.

> 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


View raw message