public interface Consumer
Service objects registered under the
Consumer interface are expected
to consume values from a Producer service via a
Wire object. A
Consumer service may poll the Producer service by calling the
Wire.poll() method. The Consumer service will also receive an updated
value when called at it's
updated(Wire, Object) method. The Producer
service should have coerced the value to be an instance of one of the types
specified by the
Wire.getFlavors() method, or one of their
Consumer service objects must register with a
service.pid and a
WireConstants.WIREADMIN_CONSUMER_FLAVORS property. It is recommended
that Consumer service objects also register with a
Exception is thrown by any of the
Consumer methods, a
WireAdminEvent of type
broadcast by the Wire Admin service.
Security Considerations - Data consuming bundles will require
ServicePermission[Consumer,REGISTER]. In general, only the Wire Admin
service bundle should have this permission. Thus only the Wire Admin service
may directly call a Consumer service. Care must be taken in the sharing of
Wire objects with other bundles.
Consumer services must be registered with their scope when they can receive
different types of objects from the Producer service. The Consumer service
WirePermission for each of these scope names.
Wireobject with an updated value from the Producer service.
Note: This method may be called by a
Wire object prior to this
object being notified that it is connected to that
When the Consumer service can receive
Envelope objects, it must
have registered all scope names together with the service object, and
each of those names must be permitted by the bundle's
WirePermission. If an
Envelope object is delivered with
updated method, then the Consumer service should assume that
the security check has been performed.
Wireobject which is delivering the updated value.
value- The updated value. The value should be an instance of one of the types specified by the
void producersConnected(Wire wires)
Wireobjects to which this Consumer service is connected.
This method is called when the Consumer service is first registered and
subsequently whenever a
Wire associated with this Consumer
service becomes connected, is modified or becomes disconnected.
The Wire Admin service must call this method asynchronously. This implies that implementors of Consumer can be assured that the callback will not take place during registration when they execute the registration in a synchronized method.
wires- An array of the current and complete list of
Wireobjects to which this Consumer service is connected. May be
nullif the Consumer service is not currently connected to any
Copyright © OSGi Alliance (2000, 2015). All Rights Reserved. Licensed under the OSGi Specification License, Version 2.0