I just spend two days writing a bunch of base-classes for JSF component-collaboration that do the lookup of related components in the tag-handler allowing you to access the other UIComponents independent from the component-tree structure easily. Just like a logical structure in parallel to the component tree for each compound-component. For ease of reuse I stored the references to the other...
All JSP, facelets and JSFTemplating make use of xml (or xml-like) syntax to define a view in JSF. All of them allow to intermix markup with components directly in the page - this is good from the perspective of a traditional web-designer, who makes the step from pure web-design to building dynamic web-frontends. A good example of a near perfect implementation of this principle is the jsfc-...
The main idea behind jsf is to have a layer of abstraction in the description and the handling of user-interface-components. The components in the component-tree itself are (conceptually) independent of their visual representation on a particular human interface device.
In reall life this fails shortly - shure you can write additional renderkits and render wml or pdf instead of html. Doing so you...
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
the first case of inter-widget-communication makes use of a high level of abstraction by using a publish/subscribe-mechanism to 'topics' and decriptive wireing called 'glue'.
The second case of widget-server...
