On 12/5/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote: > > Ok, I guess I have to fix the statement about JSF quickly, before > Craig did that :-)
:-) So, according to this: > > http://www.icesoft.com/developer_guides/icefaces/htmlguide/keyConcepts5.html > it is possible to plug into JSF lifecycle with Ajax requests and to do > partial updates. So I want to retract my claim that Ajax in JSF is a > hack. It's very much possible to integrate these things, and there's a variety of ways to accomplish what you're after ... appropriate because there is more than one architectural approach to integrating AJAX into an architecture. The ease with which this can be done is courtesy of the broad range of extensibility APIs that JSF provides. The IceSoft approach is very cool for partial page processing. You can also stroll over to MyFaces (here at Apache), or the BluePrints Catalog (at java.net) to see examples where the focus is on individual components being AJAXified themselves. Michael. Craig On 12/5/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote: > > On 12/5/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: > > > I agree with Michael. The component-oriented approach is in no way > that I > > > can see incompatible with the action-oriented model of things. > > ... > > > Frankly, an enterprising person or two could create a rather robust > > > component model layer on top of Struts without losing anything Struts > > > gives you now. Michael has already shown in practice that it's > possible. > > > > > > Oh, wait, that's basically what the Struts JSF integration library is, > > > no?!? :) As long as you like the way JSF has done it, there you go! > > > > Frank, I believe that you understand differencies between JSF > > component tree and Struts Dialogs component model. > > > > JSF builds component tree for a whole page. JSF's controller handles > > input for all components on a page. Same with Portlet API where > > request goes into Portal controller first, and *only then* delivered > > to the component. Then the page (JSF or portal, whatever) is refreshed > > as a whole. Well, there are Ajax hacks for JSF but they are what they > > are: hacks. They work around JSF component tree rendering. > > > > Components built with Struts Dialogs do not need central controller; > > request goes *directly* to the particular component. Then component > > reports back to composite page that it can refresh the view. That is > > it, pure HTTP with some dynamic JSP inclusion. > > > > In fact, components built with Struts Dialogs do not need Struts or > > other framework to support the "parent" composite page ;-) But they do > > need JSP because they are just JSP includes, nothing more. > > > > Michael. > > > > -- > > Struts Dialogs: code-behind for Struts > > http://struts.sourceforge.net/strutsdialogs/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
