Hi all, I've been exploring the jsf spec, jsf-ri-ea3 and myfaces.sourceforge.net stuff for the past few day. As a comparison, I also read through a few view state management article of asp.net. So far, I have the feeling the jsf stuff is immature ( likely to change in many place ) and a kind of heavy ( require management of a server side component tree ) compare to the asp.net approach. Which approach do yours guy think is more suitable to be implemented/adopted as the ui state management enhancement for webwork? Or may be we shall just leave thing as it is for now and wait for the dust to settle down :)
Regards, Low __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - File online, calculators, forms, and more http://tax.yahoo.com ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
