Tapestry already influences them: there are Facelets http://www.theserverside.com/news/thread.tss?thread_id=39137
That would not help much IMO because of JSF's brurry focus, JSF promises to do everything for everybody. Lovest common denominator is not that attractive. EntityBeans tried and faded away (although Entity Managed Beans make sense in some cases, not those stupid CMPs). JDO is bad by the very same reason. I like Unix spirit: do one thing but do it really well. Then bigger systems can be built by combining those basic components. There are different APIs and tricks for reasons, endless attempts to treat apples and oranges alwais like abstract fruit do not make much sense IMO. Peter Svensson <[EMAIL PROTECTED]> wrote: Well, they're more consultant-friendly :-)= Stands to reason. I would bet that the next version of JSF will be as inspired by Tapestry as EJB3 was of Hibernate. Cheers, PS On 3/10/06, Wayland Chan wrote: > > I'm fairly suprised that JSF and especially Spring's Web MVC were so high. > Literally shocked that Spring's Web usage was higher than Tapestry and > WebWork combined. > >
