[
https://issues.apache.org/jira/browse/SLING-9895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-9895.
-------------------------------------
Resolution: Fixed
Added two new boolean methods to the HandlerContext
https://github.com/apache/sling-org-apache-sling-feature/commit/5c446a04d85dfc2407665749e5f0bf900dc02efe
> Provide more information to extension handlers
> ----------------------------------------------
>
> Key: SLING-9895
> URL: https://issues.apache.org/jira/browse/SLING-9895
> Project: Sling
> Issue Type: Improvement
> Components: Feature Model
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: Feature Model 1.2.14
>
>
> Extension handlers get a source and a target and are invoked to merge the
> source into the target. For example if two features are aggregated, a handler
> is invoked twice, the target is always the resulting feature and the source
> is the first feature and then the second feature.
> If an extension handler wants to act on data of the aggregated features
> (first and second feature in this case), the handler does not have a clue
> when it is invoked about the state.
> In addition, the same handlers are also used to process a prototype feature -
> in some cases processing of prototypes might be different from aggregation
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
