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 2014/02/28 11:07:24 UTC

[jira] [Commented] (OAK-1474) ConfigurationBase must not use 'componentAbstract'

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

angela commented on OAK-1474:
-----------------------------

anything else you want to do on this issue in addition to the changes commited in r1572672?
i tentatively scheduled this for 0.19.

> ConfigurationBase must not use 'componentAbstract'
> --------------------------------------------------
>
>                 Key: OAK-1474
>                 URL: https://issues.apache.org/jira/browse/OAK-1474
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Tobias Bocanegra
>            Assignee: Tobias Bocanegra
>             Fix For: 0.19
>
>
> the {{@Component(componentAbstract = true)}} annotation is deprecated because it is considered dangerous as it stipulates modular extensibility. the problem is that implementing components need to be re-analyzed by the scr plugin to react on eventual DS changes in the abstract component.
> {{org.apache.jackrabbit.oak.spi.security.ConfigurationBase}} is using the {{@Activate}} annotation which is a problem if overriding classes don't call super.activate(). I suggest to introduce a better mechanism to initialize the class.



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