Jonas and John, Weblets and Mabon where born during your research for the book. As best I now you have a tremendous experience working on ADF Faces, previously. Those two open source projects sound like huge steps aside of the ADF Faces architecture (They are still about JSF, no doubt here). If somebody ask me how I can characterize those projects in one word, I can say - simplification. It is right opposite to ADF, actually. As we know, ADF Faces is already donated. So, my question is Did the book become a measure for you to realize what should go forward and what should be left in the past? [ April 05, 2006: Message edited by: Sergey Smirnov ]
When we started our book project we had set out to create a book that would cover all aspects of JSF component development, not just creating a simple UI component. At the time ADF Faces was still a property of Oracle and we were legally bound to not discuss the internals of it e.g. concerns about IP.
This forced us to come up with new solutions to some of the problems already solved by ADF Faces and other component libraries.
Of the two projects - we actually have a third project D2, but we can leave that out for now [shameless pitch] - Weblets is the project that solves an issue that for example ADF Faces, MyFaces, Backbase and others have already provided unique solutions for - resource loading. Weblets is solving the resource loading issue with a goal to simplify resource loading not only for component developers, but most importantly for application developers using JSF component libraries.
Mabon on the other hand is a new project that provides a solution that allow component developers to utilize JSF's managed bean facility to deliver data to Ajax-enabled JSF components. This is currently not available in ADF Faces.
We are of course happy to have been able to come up with these solutions and we hope that component developers will like them as much as we do.
Following up on weblets: Have you made tests in a non-JSF-environment? I think that it's idea might solve problems that lots of web-applications have, as soon as they must be deployed using automated procedures...