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/14 19:58:31 UTC
[jira] Created: (FELIX-632) Component are set to immediate despite
they are already immediate
Component are set to immediate despite they are already immediate
-----------------------------------------------------------------
Key: FELIX-632
URL: https://issues.apache.org/jira/browse/FELIX-632
Project: Felix
Issue Type: Bug
Components: iPOJO
Affects Versions: iPOJO-0.8.0
Reporter: Clement Escoffier
Assignee: Clement Escoffier
Priority: Trivial
A recent improvement allows iPOJO to detect if a component should be immediate or not. However, the actual implementation introduces a small issue. A component specifying its immediate attribute to true, they iPOJO overrides this. Of course, this has no impact, but could be avoided.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-632) Component are set to immediate despite
they are already immediate
Posted by "Clement Escoffier (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Clement Escoffier resolved FELIX-632.
-------------------------------------
Resolution: Fixed
Fix in the revision 676672
Improves immediate component detection in order to avoid to re-set a component as immediate when it is already immediate. The detection is applied only when the immediate attribute is not set.
> Component are set to immediate despite they are already immediate
> -----------------------------------------------------------------
>
> Key: FELIX-632
> URL: https://issues.apache.org/jira/browse/FELIX-632
> Project: Felix
> Issue Type: Bug
> Components: iPOJO
> Affects Versions: iPOJO-0.8.0
> Reporter: Clement Escoffier
> Assignee: Clement Escoffier
> Priority: Trivial
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> A recent improvement allows iPOJO to detect if a component should be immediate or not. However, the actual implementation introduces a small issue. A component specifying its immediate attribute to true, they iPOJO overrides this. Of course, this has no impact, but could be avoided.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.