You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2013/02/14 19:23:12 UTC

[jira] [Commented] (OAK-625) Ability to pass workspace name to a CommitHook

    [ https://issues.apache.org/jira/browse/OAK-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13578544#comment-13578544 ] 

angela commented on OAK-625:
----------------------------

added an initial draft in revision 1446289 that works with our current single-workspace setup:
instantiation of the security related commit hooks is postponed to the Oak#createContentRepository 
call when the default workspace name is known -> passing in the workspace name to the hook constructors
where needed.

leaving this issue open for further processing. in particular in the light of OAK-627 we might have
the ability to solve this in a far less hacky way.
                
> Ability to pass workspace name to a CommitHook
> ----------------------------------------------
>
>                 Key: OAK-625
>                 URL: https://issues.apache.org/jira/browse/OAK-625
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: angela
>            Assignee: angela
>
> as discussed recently on the mailing list, there are cases where the
> name of the editing workspace should be known within the commit hook.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira