[ 
https://issues.apache.org/jira/browse/OAK-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jukka Zitting resolved OAK-1387.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 0.17
         Assignee: Jukka Zitting

Patches committed in revisions 1566767 and 1566769. Resolving this as fixed, 
let's follow up in a separate issue about how this change can be leveraged by 
the security components.

Actually the {{ValidatorProvider.getRootValidator}} method should be declared 
as {{\@CheckForNull}} for consistency with {{EditorProvider}}. I changed that 
in revision 1566789.

> Pass CommitInfo to commit hooks, editors and validators
> -------------------------------------------------------
>
>                 Key: OAK-1387
>                 URL: https://issues.apache.org/jira/browse/OAK-1387
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: core
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>             Fix For: 0.17
>
>         Attachments: 
> 0001-OAK-1387-Pass-CommitInfo-to-commit-hooks-editors-and.patch, 
> 0002-OAK-1387-Pass-CommitInfo-to-commit-hooks-editors-and.patch
>
>
> In OAK-144 we introduced the {{CommitInfo}} object for observation purposes. 
> It's passed along with custom commit hooks to the {{NodeStore.merge()}}.
> It turns out that the custom commit hooks coming from 
> {{AbstractRoot.getCommitHook()}} are constructed using information that could 
> well be passed through the {{CommitInfo}} object. This would simplify things 
> as all hooks that apply to a commit could be accessed through the whiteboard 
> as normal services.
> Doing this would require us to extend the amount of information that can be 
> passed through the {{CommitInfo}} object, and adjust the {{CommitHook}}, 
> {{EditorProvider}} and {{ValidatorProvider}} interfaces to accept also a 
> {{CommitInfo}} argument. None of this seems too troublesome.
> WDYT?



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to