Sequence numbers for a given event ID are strictly increasing. If there is no gap between two sequence numbers, no events have been missed; if there is a gap, events might (but might not) have been missed. For example, a gap might occur if the lookup service crashes, even if no events are lost due to the crash. @author Sun Microsystems, Inc. @since 1.0
{@code ServiceEvent} objects are delivered to {@code ServiceListener}s and {@code AllServiceListener}s when a change occurs in this service's lifecycle.
A type code is used to identify the event type. @author thomas.diesler@jboss.com @since 27-Sep-2013 @see ServiceListener @see AllServiceListener @Immutable
Refer to {@link ServiceEventsSupport} for more information. @author Yohan Liyanage @version 1.0 @see ServiceEventsSupport @see ServiceHookCallback @see ServiceMessage
{@code ServiceEvent} objects are delivered to {@code ServiceListener}s and {@code AllServiceListener}s when a change occurs in this service's lifecycle. A type code is used to identify the event type for future extendability.
OSGi Alliance reserves the right to extend the set of types. @Immutable @see ServiceListener @see AllServiceListener @author $Id: b27a941cb68e6416825b1b717090a2eb098733f3 $
|
|
|
|
|
|
|
|
|
|
|
|