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 "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2014/02/27 00:01:19 UTC
[jira] [Updated] (OAK-1474) ConfigurationBase must not use
'componentAbstract'
[ https://issues.apache.org/jira/browse/OAK-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tobias Bocanegra updated OAK-1474:
----------------------------------
Description:
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.
{{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.
was:
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.
{{ConfigurationBase}} is not using any DS or metatype annotations and we should just remove the annotation.
> ConfigurationBase must not use 'componentAbstract'
> --------------------------------------------------
>
> Key: OAK-1474
> URL: https://issues.apache.org/jira/browse/OAK-1474
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Reporter: Tobias Bocanegra
> Assignee: Tobias Bocanegra
>
> 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.
> {{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)