Travis Reeder schrieb: > I've been thinking about this same issue lately, it seems to me that the > only component that must stores it's data in the session is the > DataTable (the DataModel may be lazy, but it still must be in the > session) and other Collection based components like dataList. Other > components don't necessarily have this requirement, you can bind > output's and inputs to request based objects. > > I got to thinking how this issue could be overcome and generally in > non-jsf apps, you use some "id" field in the object to identify the item > in a list. So what if you could specify on the dataTable an > "identityField" attribute like <t:dataTable identityField="id"... Then > on the backend instead of trying to match up object identity, we can > just match up the identityField. This way, you could reload the data > each request and wouldn't have to worry if the list changed in the > database because you would only try to find the matching identity field. > I personally think this is a perfect case for a seam like conversation based system, the same goes for the ejb3 entity manager or generally a connection session handler.
