Ok, I'm obviously not being very clear.
I have a conversation scoped bean which contains a List. The List is outjected
using @DataModel(value="model", scope = ScopeType.PAGE). The DataModel is then
used in the normal way:
<h:dataTable value="#{model}" var="row">...
Now when the response is submitted I understand that a serialized version of
the component tree must be sent from the client, but I'd imagine those contents
contain an HtmlDataTable that binds to the outjected DataModel, not the List
that the DataModel wraps. Now the response is recieved, the component tree is
deserialized including the DataModel and it does it's thing, namely, setting
the correct @DataModelSelection. That explains why the selection has been
serialized/deserialized, but the original List which was wrapped and is a field
in the conversation scoped bean is also overwritten with the
serialized/deserialized values. I can't see why that is necessary and, on top
of it, it seem to me that if the two versions of the List were checked for
equality the original list could simply be reused in most situations.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3949901#3949901
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3949901
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
