On 7/11/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote: > JSF still differentiates "real" object (whatever it might be, a real > business object or a VO) from visual component data, which I don't > like. From my point of view, it is much easier to have an object with > an ID, to view/edit it, or to delete it. Therefore, I do not need > viewstate for UI components. I only need to store my object somewhere > like in session while I work with it. I want my widgets and my view to > be as dumb as possible. All data and state that I need is in real > objects, I do not need artificial viewstate to duplicate it.
Before anyone corrects me, I want to say that I went a little overboard ;) There are selection lists, treeviews and other objects which do not have direct representation in the domain model. These objects should be maintained by web framework. I was talking primarily about input/output panels and about item lists. Well, item list may be also considered as pure view object, consisting of business objects... Whatever. In this case I was talking about input/output panels only ;-) Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
