title: Which EventBus is preferable for new Desktop Applications?
body: <p>For several years we use <code>org.bushe.swing.event.EventBus</code> for mainly swing desktop applications. The API is really consistent, and easy to use. But now new requirements have arrised and its desired, that some EventSubscribers should get prefered over others, since they are informed synchronisly. So some kind of priority factor is needed for those subscribers.</p>
  
  <p>Extending EventBus to priorize EventSubscribers shouldnt be that much of a problem, but since <code>org.bushe.swing.event.EventBus</code> has gone stale, I am not sure, if it might be preferable to change the EventBus Implementation. </p>
  
  <p><a href="http://eventbus.org/">org.bushe.swing.event.EventBus</a> itself recommends projects like <a href="http://google-web-toolkit.googlecode.com/svn/javadoc/2.1/com/google/gwt/event/shared/EventBus.html">GWT Eventbus</a> for GWT. I'm not sure, if that is also a good approach for swing applications. Which EventBus Implementations do you usually use? Do you may even know a simple Implementations which supports Priorities for Subscribers?</p>