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

Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2019/08/15 08:07:00 UTC

[jira] [Resolved] (SLING-8631) Introduce state for extensions

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

Carsten Ziegeler resolved SLING-8631.
-------------------------------------
    Resolution: Fixed

Added the new state, deprecated old methods and adjusted reader/writer

> Introduce state for extensions
> ------------------------------
>
>                 Key: SLING-8631
>                 URL: https://issues.apache.org/jira/browse/SLING-8631
>             Project: Sling
>          Issue Type: New Feature
>          Components: Feature Model
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: Feature Model 1.1.0, Feature Model IO 1.1.0
>
>
> Currently an extension is either required or optional. However, the extensions of the feature model also allow to keep transient state like a cache of calculations. For example, the result of scanning a feature could be attached to a feature model to avoid rescanning of downstream users.
> Therefore we should probably add a method to get the state of an extension with the values TRANSIENT,OPTIONAL,REQUIRED



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)