[
https://issues.apache.org/jira/browse/OAK-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13640436#comment-13640436
]
Alex Parvulescu commented on OAK-673:
-------------------------------------
After discussing this with Jukka, it looks like the work here is sufficient.
Putting *everything* in a single composite editor is not something we can do
now, so this is as far as it makes sense to go here.
Some editors cannot currently live together as they will be ignorant of each
other's changes to the content (like for ex versioning and indexing). The
simplest fix is to not put them together.
We'll revisit this later on if it turns out we can shuffle/regroup the existing
editors into more efficient composite ones.
> Unified hook processing
> -----------------------
>
> Key: OAK-673
> URL: https://issues.apache.org/jira/browse/OAK-673
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: core
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Attachments: OAK-673-VersionHook.patch
>
>
> As [discussed|http://markmail.org/message/xqw3yg3z5rnsiwz3] on oak-dev@, it
> would be good reduce the number of separate content diffs that various hooks
> do during each commit. To do this without having to merge unrelated
> functionality into one big hook class we should come up with a new hook
> generalization, like the one I
> [proposed|http://markmail.org/message/bydje7rf3si67fc3], that allows multiple
> independent components to process the results of a single content diff.
--
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
