In the wsn-consumer example, the code shows how to register a resource
as a notification consumer. Then, to receive the notifications, the
NotificationMessageListener interface must be implemented. In the
example, this is done by a ConsumerCapabilityImpl capability class
associated with the "consumer" resource.
My question is: how does Muse know what resource component to call in
order to pass the notification message? Does it scan thru the consumer
resource's list of capability classes and invoke the one the implements
the NotificationMessageListener interface? The muse.xml descriptor file
doesn't seem to have a place to explicitly tell Muse what class to call,
but somehow Muse knows already.
So what happens if my resource has 2 capability classes, both of which
are NotificationMessageListeners. How does Muse know which one to call?
There's also the case where each of the 2 capability classes can be
listening to notifications from different producers (i.e. different Muse
applications).
