"dbatcn" wrote : Putting a little information about this (dependence or lack thereof of javascript) in the Seam documentation area would be very helpful I think, particularly to people like me new to Seam/JSF/facelets/MyFaces/EJB3/JavaPersistence. Completly agree, it looks like seam documentation assumes some degree of competency with JSF, EJB (less in v3 due to Pojos but container managed concepts are needed, and other basics). Maybe a section like: "Things to Know About Underlying Frameworks in Seam" would be a good idea. In particular Seam has been a breeze for me as I'm very close to JSF, EJB and Java5, but to compete (catch up?) with Rails some minimal background in underlying frameworks is needed, and that could be a consideration for many as you mentioned Java developers. In regards to your original question, what about creating (or reusing) a pluggable JSF renderer. Something that Seam would be somewhat agnostic to -if not mistaken- Jsf renderers idea was that in principle: to server different clients. Yeyo "dbatcn" wrote : | I think that there's a large population of people like me who are Java-competent who need to create web apps and trying to decide whether to go forward with more recent Java stuff or move (defect?) to Ruby on Rails. Anything that gets people like this going will be hepful. I will admit as a newbie to this that the boundaries between the several projects/APIs I mentioned above are only slowly becoming clear, even with considerable reading from several sources. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956816#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...