Re: [jsr-314-open-mirror] [jsr-314-open] Fwd: Fix UIData state saving model

>>>>> On Wed, 25 Aug 2010 20:12:59 -0500, Leonardo Uribe <lu4242(a)gmail.com&gt; >>>>> said: LU> The problem with allow it with a context-param is there is no way to LU> "reset" the deltas or remove rows to synchronize the model with the LU> component state. LU> Suppose a simple use case, where there is a datatable and an option LU> that removes one row. Since we don't have a way to notify the LU> component that the row has been removed the state of the deleted row LU> will be applied on the next one. Ok, I see. Now, when I discussed with the expert community at a recent meeting the process for accepting new features for 2.1, I tried to be as clear as possible that we'd need the contributing party to do *all* of the work. Leorando, you've done the code, and it's great, but the spec language is even more important since this body, technically, is partially responsible for the spec. Oracle, as the sponsor, is solely responsible for the impl. Now, as I said, I'm delighted with your contribution of an implementation for this feature, but I need you to author as much as possible of the spec text. I've started by documenting the preserveRowComponentState property in the UIData.setPreserveRowComponentState() method. Please take a look at the javadoc I've generated in this attachment [1] to issue 153 [2]. I've posed some questions in there, you can anwser them here. Also, please correct my where I've gone wrong. If you could submit a text file with sketches of the javadoc for other elements of this feature, for example, the new TransientStateHelper interface, it would really increase the likelihood of this feature making it into 2.1. [1] https://javaserverfaces-spec-public.dev.java.net/nonav/issues/showattachm... [2] https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=153 -- | edward.burns(a)oracle.com | office: +1 407 458 0017 | homepage: | http://ridingthecrest.com/ | 12 work days until JSF 2.1 Milestone 3