You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2014/08/06 04:04:12 UTC
[jira] [Updated] (FELIX-4507) [DS] "persistent" factory components
[ https://issues.apache.org/jira/browse/FELIX-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks updated FELIX-4507:
--------------------------------
Fix Version/s: (was: scr-1.8.2)
scr-2.0.0
> [DS] "persistent" factory components
> ------------------------------------
>
> Key: FELIX-4507
> URL: https://issues.apache.org/jira/browse/FELIX-4507
> Project: Felix
> Issue Type: New Feature
> Components: Declarative Services (SCR)
> Affects Versions: scr-1.8.0
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: scr-2.0.0
>
>
> The lifecycle constraints of factory components make them generally useless. This introduces a different kind of factory component where:
> - the componentFactory service is always registered irrespective of whether any references are available
> - the components created by newInstance act like regular components created by config admin factory pids; the component is present whether or not references are available and the instance comes and goes as references come and go. Calling dispose removes the component.
> - a modify method is added to the ComponentInstance returned from newInstance. (the ComponentInstance implements a new, extension, interface with the modify method)
> There are some consequences, such as ComponentInstance.getInstance() may return null and may not always return the same object.
> This behavior can be turned on for a particular component with a "extension" attribute in the component descriptor
> xmlns:felix="http://felix.apache.org/xmlns/scr/extensions/v1.0.0"
> felix:persistentFactoryComponent="true"
--
This message was sent by Atlassian JIRA
(v6.2#6252)