It'd be nice to allow a component to logically subscribe to the output of a component to support 1-many distribution - i.e. like JMS topics.
Right now a component can output a one-way and not really care where it goes - letting the NMR do the routing. So we should provide a 'service subscription' model on a component to be able to do 1-many routing.
e.g.
each component's ActivationSpec could have a collection of Subscription objects, each subscription object could be something like...
class Subscription { QName serviceName QName interfaceName QName operationName String endpoint Filter filter }