The JSF is an event-based framework with tight coupling in a page-based controller. That should answer the question in itself. If you want that, then you will put up with the performance and CPU hit. You might even put up with the performance and CPU hit if you are hell bent on using tools instead of custom coding. I think the tool boys are really not saving in the long run because too much is left to a lack of knowledge which will cost in the long run with maintenance headaches. But, pushing a button is faster than coding at the beginning: no doubt about that.
On 5/10/05, Yan Hu <[EMAIL PROTECTED]> wrote: > Hi: > I have been playing with JSF lately. I really like it since it is very > intuitive. But as I > understand it, JSF keeps a component tree for each page with JSF widgets in > it on the server. So > it is heavy weight compared with struts. Could I safely say that struts-based > apps are a bit more > performant than JSF ones? someone please shed some light on it....... > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- "You can lead a horse to water but you cannot make it float on its back." ~Dakota Jack~ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
