All,<div><br></div><div>I'd like some feedback on the following. �I brought up an idea for defining configuration for the forwarding of events over JMS in our weekly meeting on (4/29/2010). �The basic idea is that users should be able to easily configure which events get forwarded to which destinations. �A user should be able to define a mapping of event types to destinations in a bean (and then optionally in xml using seam-xml). �This might look like:</div>
<div><br></div><div>class JmsForwardingObserver implements ObserverMethod</div><div>{</div><div>�� JmsForwardingConfiguration config;</div><div>�� ...</div><div>}</div><div><br></div><div>class JmsForwardingConfiguration</div>
<div>{</div><div>�� // Destinations to forward to</div><div>�� Set<? extends Destination> getDestinations();</div><div>�� // Event types to observer and forward</div><div>�� Set<? extends Event<?>> getEventTypes();</div>
<div>}</div><div><br></div><div>By default, we would create an instance of�JmsForwardingObserver�for every registered JmsForwardingConfiguration. �The user could also register their own�JmsForwardingObservers�to handle special forwarding requirements. �And this could all be done with seam-xml-bean-config if the user chooses.</div>
<div><br></div><div>Is there a preferred way to allow users to configure aspects of a module yet?</div>
<div><br></div><div>In the meeting I mentioned an annotation-based configuration but on second thought I'm not sure how that would work to define sets of destinations or events cleanly.</div><div><br></div><div>WDYT?</div>
<div><br>-- <br>Jordan Ganoff<br>
</div>