Kito D. Mann wrote: >>>At this point, with the clear promise of AJAX, I cannot see >> >>any reason >> >>>to give up Struts and go to JSF. If I was starting a new web >>>application today, I would use Struts and AJAX. >> >>Not that I going to jump JSF anytime soon, but: >>http://www.icesoft.com/products/icefaces.html > > > Admittedly, I'm on the JSF bandwagon, but people often don't realize that > JSF and Ajax go hand-in-hand. It's just that you don't have to code it > yourself, which is, after-all, the whole point of JSF (components). > > Most component vendors are adding Ajax support already. For example, see: > http://www.otrix.com/demos/webTree/dimensions/index.faces. > Yes, even MyFaces already has some ajax components in there, the main problem is, that both architectures are a little bit rough to marry, once you evolve from the basic we read data and display it stage. Because JSF requires to have a backend component tree and ajax basically might interfere with the normal jsf mechanisms. But apparently most of those problems are solved otherwise things like IceFaces would not exist by now, or the MyFaces updatable datatable. Apparently a future JSF spec will solve most of those problems on spec level, probably by introducing an ajax based lifecycle or lifecycle step, which in my opinion would be the cleanest way to resolve those issues.
Also marrying the JSF event system with ajax might be sort of problematic because JSF events evolve around the fact you run into a refresh every time you do something, while ajax evolves around the idea of having sort of a rich client event system which tries to minimize roundtrips. But that is a general problem of marrying html with something more rich client side thing. But none of those issues shoule be problematic for the average users, because most of the power of jsf revolves around the idea of having components and to keep all the javascript, whatever stuff on the component builder side of things. An idea which seemed to work out quite nicely although the component programming model of JSF itself is a tad too complex, due to its openness, but it worked out given the huge number of components and component set already available. Sun really has hit a spot there. Werner --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
