>I guess I look at this stuff much differently with JSF. Watching Ted >Neward's interview on SOA >(http://www.theserverside.com/news/thread.tss?thread_id=39757), it got >me thinking that these AJAX solutions are doomed to pursue the same route.
[OT] I have only listened to the first 15 minutes. Neward is a smart guy but I don't buy the "Spouse" example. Although a spouse href can point to a cat, he does not mention that modelling that relationship in Java has it's limitations as well. For example, there is no way to guarantee this in any language: dennis.getSpouse() == tatiana & tatiana.getSpouse() == dennis (which is true in XML also). A better way to model that situation would be to just create a marriage class. >If we setup a good story for partial processing/rendering on the server, >then there's no real need for intermediary RPC solutions from a pure >data standpoint. Send up some parameters over AJAX, and then let JSF >coordinate what needs to be re-rendered without wasteful marshalling of >unneeded data over the network. What do you mean by partial processing/rendering ? I am suggesting *less* network activity, although the kinds of developers who are aroused by this kind of thing often do have a fetish for asyncronous solutions. Sometimes I have a hard time "selling" JSF because end users don't want to wait for the round trip each time the page dances. Dennis Byrne
