This sounds like you could use an Event Bus, also called "Event Collaboration" pattern; see http://martinfowler.com/eaaDev/EventCollaboration.html for more on it.
Basically, the idea is that whenever something "interesting" happens, a Composite raises an event, which all other composites get a chance to process. Most composites will just simply "let it pass", but those who find it relevant, can update themselves. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
