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 2009/04/05 16:07:13 UTC
[jira] Resolved: (FELIX-1024) iPOJO imposes to get an empty
constructor if another constructor exists
[ https://issues.apache.org/jira/browse/FELIX-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Clement Escoffier resolved FELIX-1024.
--------------------------------------
Resolution: Fixed
Fixed at revision 762084.
iPOJO does no more requires a "suitable" constructor. If (and only if) none found, one is injected:
public ClassName(InstanceManager im) {
super();
_setInstanceManager(im);
// Return
}
> iPOJO imposes to get an empty constructor if another constructor exists
> -----------------------------------------------------------------------
>
> Key: FELIX-1024
> URL: https://issues.apache.org/jira/browse/FELIX-1024
> Project: Felix
> Issue Type: Bug
> Components: iPOJO
> Affects Versions: iPOJO-1.2.0
> Reporter: Clement Escoffier
> Assignee: Clement Escoffier
> Fix For: iPOJO-1.4.0
>
>
> If a component contains a constructor with arguments (others as the bundle context), iPOJO asks for an empty constructor to create the pojo object.
> This constructor can be introduced automatically during the manipulation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.