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 2013/02/26 14:48:13 UTC
[jira] [Assigned] (FELIX-2773) Automatic restart of iPOJO instance
on configuration update
[ https://issues.apache.org/jira/browse/FELIX-2773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Clement Escoffier reassigned FELIX-2773:
----------------------------------------
Assignee: Clement Escoffier
> Automatic restart of iPOJO instance on configuration update
> -----------------------------------------------------------
>
> Key: FELIX-2773
> URL: https://issues.apache.org/jira/browse/FELIX-2773
> Project: Felix
> Issue Type: Improvement
> Components: iPOJO
> Affects Versions: iPOJO-1.6.0
> Reporter: Bengt Rodehav
> Assignee: Clement Escoffier
> Priority: Minor
>
> I use iPOJO and configuration admin. When certain configuration properties change, I want to "restart" my iPOJO instance. I e I want the instance to become invalid and then valid again. Currently I do some initialisation on the method marked as @Validate and some cleanup in the method marked as @Invalidate.
> It's very tricky to get this to work. When I start my application it seems like both the @Validate and the @Updated methods are called which causes problems. Ideally I would like to mark my iPOJO properties as requiring the instance to "restart", e g
> @Property(name = "rootUrl", restart = "true")
> private String mRootUrl;
> Whenever the "rootUrl" property of my instance is reconfigured, the iPOJO instance would be invalidated and then validated again (if it is valid of course).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira