In ICEfaces 1.8, we employ several strategies for saving component fields, when in a UIData container, so that the field value will be distinct per UIData row. Sometimes we keep a Map<String clientId, Object field> and sometimes we use the SeriesStateHolder interface. In OutputResource, we found that we could not use the clientId, since if the OutputResource was in a UIData whose data model was having insertions or deletions, then the clientIds would not match up any more, which would break both of the previously mentioned strategies. One strategy that seems to work well, in all scenarios, is using settable properties, and making the app store the value in the row level object. The worst strategy is doing nothing, and applications unexpectedly failing.

Whichever strategy we use, it would be nice if we could just specify that a property should be unique per UIData row, and have the generator create the appropriate getter and setter methods to handle that.