{@code ConfigurationEvent} objects are delivered to all registered{@code ConfigurationListener} service objects. ConfigurationEvents must beasynchronously delivered in chronological order with respect to each listener.
A type code is used to identify the type of event. The following event types are defined:
Security Considerations. {@code ConfigurationEvent} objects do not provide{@code Configuration} objects, so no sensitive configuration information isavailable from the event. If the listener wants to locate the {@code Configuration} object for the specified pid, it must use{@code ConfigurationAdmin}. @see ConfigurationListener @Immutable @author $Id: b6e83bbc54df92df81679969a438545d8161978f $ @since 1.2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|