Web Applications
Finally it's being done - jMaki's publish/subscribe message-bus extends to the server!
If you are writing cooperating components (compound components) for JSF you most likely want free and easy access from each component your compound component is build of to each other. To archive this you need references to these other components - JSF 1.2 lets you get these using findComponent or you may walk the component-tree yourself to do so. But if you try to store references to other UIComponents in you components state for later reuse these references will not survive clientside statesaving.
the templating techniques available (or better: that I'm familiar with) that allow to define a view in JSF have one thing in common: if you intermix static-markup with components, the structure of your markup will also define the structure of the resulting component tree. Here are some thoughts on the implications and how to overcome these.
even if the spec claims it's not true, JSF 1.2 is quite tightly coupled to http and you will have a hard time to use in other context than that. Ever tried to do something with the component-tree while there's no request from a browser like sending a jms-message directly to a component?
the jMaki widget model allows for two ways of communication: there is in-page communication from one widget to others on the same page and communication in between a widget and the server
