jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Bocanegra (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2209) Versioning operations should be done on the workspace
Date Sun, 19 Jul 2009 00:14:14 GMT

    [ https://issues.apache.org/jira/browse/JCR-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732949#action_12732949

Tobias Bocanegra commented on JCR-2209:

proposed patch in sandbox: https://svn.apache.org/repos/asf/jackrabbit/sandbox/tripod-JCR-2209

there is one nasty hack: in order to access another workspace for the merge operations, the
version manager needs to create a new session. this is currently done using the RepositoryImpl.createSession(subject,
string), which is protected. the only solution i see so far would be (other than making this
method public) to move the JcrVersionManager to org.apache.jackrabbit.core.

> Versioning operations should be done on the workspace
> -----------------------------------------------------
>                 Key: JCR-2209
>                 URL: https://issues.apache.org/jira/browse/JCR-2209
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: versioning
>            Reporter: Tobias Bocanegra
>            Assignee: Tobias Bocanegra
>             Fix For: 2.0.0
> currently all versioning operations modify the transient states of the items where the
operation is executed although all operations are workspace operations.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message