You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Clement Escoffier (JIRA)" <ji...@apache.org> on 2008/07/11 11:00:31 UTC
[jira] Resolved: (FELIX-631) Immediate Component Detection
[ https://issues.apache.org/jira/browse/FELIX-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Clement Escoffier resolved FELIX-631.
-------------------------------------
Resolution: Fixed
Fix the 675866 revision
Add a detection mechanism to set component to immediate when they don't provide services and do not specify that they are not immediate ("immediate="false""). This detection is not applied for handlers. Handlers are never immediate, as their lifecycle is attached to the instance lifecycle.
> Immediate Component Detection
> -----------------------------
>
> Key: FELIX-631
> URL: https://issues.apache.org/jira/browse/FELIX-631
> Project: Felix
> Issue Type: Improvement
> Components: iPOJO
> Affects Versions: iPOJO-0.8.0
> Reporter: Clement Escoffier
> Assignee: Clement Escoffier
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> In order to set a component as immediate, the developer have to write immediate="true" in the component type description. To avoid this, it is possible to detect when a component must be immediate based on simple heuristics (as specified in SCR). This improvement will reduce a little the among of metadata to write.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.