[
https://issues.apache.org/jira/browse/FELIX-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932884#action_12932884
]
Bengt Rodehav commented on FELIX-2694:
--------------------------------------
Unfortunately there seems to still be some problems regarding this.
Consider this scenario:
1. I create an invalid configuration, that will cause my start() method to
throw an exception.
2. iPOJO stops the instance
3. I repair my configuration
4. iPOJO recognizes a configuration change and calls my start() method again
5. At this point, my configuration settings do not seem to be set.
E g I have these configuration settings:
private String mName;
private String mPid;
@Property(name = "name", mandatory = true)
public void setName(String theName) {
mName = theName;
}
@Property(name = org.osgi.framework.Constants.SERVICE_PID, mandatory = true)
public void setPid(String thePid) {
mPid = thePid;
}
Normally (when my instance is successfully started the first time), these
values are correctly initialised in my start() method. However, in the scenario
described above, these values are null. This causes the start() method to fail
again.
> Instance state not recomputed after reconfiguration when the instance is
> stopped
> --------------------------------------------------------------------------------
>
> Key: FELIX-2694
> URL: https://issues.apache.org/jira/browse/FELIX-2694
> Project: Felix
> Issue Type: Bug
> Components: iPOJO
> Reporter: Clement Escoffier
> Assignee: Clement Escoffier
> Fix For: iPOJO-1.8.0
>
>
> When a component instance is stopped and reconfigured, the instance state is
> not recomputed. The instance must be restarted with the new configuration.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
