[#FELIX-601] Reactivation of a component after a configuration update should be completely asynchronous

Felix

Reactivation of a component after a configuration update should be completely asynchronous

Created: 06/Jun/08 01:49 PM Updated: 10/Jun/08 08:40 AM

Return to search

Component/s:

Declarative Services (SCR)

Affects Version/s:

scr-1.0.2

Fix Version/s:

scr-1.0.2

Time Tracking:

Not Specified

Resolution Date:

10/Jun/08 08:40 AM

Description

« Hide

Currently the component is taken down immediately upon receiving new configuration. This may create issues when components are currently being activated. Therefore the cycling of the component after receiving configuration is to be scheduled for asynchronous execution.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

Felix Meschberger made changes - 06/Jun/08 01:49 PM

Field	Original Value	New Value
Status	Open [ 1 ]	In Progress [ 3 ]

Repository	Revision	Date	User	Message
ASF	#663943	Fri Jun 06 13:52:00 UTC 2008	fmeschbe	~~FELIX-601~~ Reactivation upon reconfiguration happens completeley asynchronous ~~FELIX-599~~ add a log message indicating successful wait for the service registration lock
				Files Changed
				MODIFY /felix/trunk/scr/src/main/java/org/apache/felix/scr/impl/ImmediateComponentManager.java MODIFY /felix/trunk/scr/src/main/java/org/apache/felix/scr/impl/AbstractComponentManager.java

[ Permlink | « Hide ]

Felix Meschberger added a comment - 06/Jun/08 01:52 PM

Implemented completely asynchronous cycling after configuration update in Rev. 663943

[ Permlink | « Hide ]

Felix Meschberger added a comment - 10/Jun/08 08:40 AM

This has been implemented and verified and can be closed.

Felix Meschberger made changes - 10/Jun/08 08:40 AM

Resolution		Fixed [ 1 ]
Status	In Progress [ 3 ]	Closed [ 6 ]