> One thing I am finding is for annotations and auto-registering, that the > machinery dominates the actual messaging code in ApplicationContext.
ApplicationContext is large, but the message handling code itself is pretty small - it is just a few methods: subscribe() unsubscribe() sendMessage() queueMessage() I have actually been wondering if it might make sense to move it to a core class, such as org.apache.pivot.util.MessageBus so that non-UI applications can also use it. The only thing specific to WTK is queueMessage(), but that could either remain in ApplicationContext and be implemented in terms of MessageBus, or it could potentially be eliminated - the code in that method could easily be implemented at the application level.
