I looked at the
JSF example in the article. At the same time, I tried imagining the equivalent tapestry4 code to achieve the same.
Somehow I feel that very few people would actually pick JSF after looking at the comparison ( just my personal opinion). What do you think? Would that be fair to JSF?. May be
you should pick another example that demonstrates that JSF is superior to tapestry wrt some other aspect (if at all)...just an opinion.
Update: Ok i take it back. May be the users can decide for themselves as you point out. But some of the obvious observations like the absence of another indirection in the form of navigation rules, the most sighted reason of the template being viewable in any editor / browser and access to any model/bean without any explicit configuration (Ok hivemind if something needs to be maintained in session) made me feel that tapestry w'd be a clear winner wrt this use case.
Can you modify the example to include dynamic component creation? I mean we s'dnt know until run time what component actually needs to be rendered.
I mean something along the lines of
if(something) componentTree.add(new Button());
[ January 17, 2006: Message edited by: Karthik Guru ]
