On Nov 23, 2007 2:21 PM, Johan Compagner <[EMAIL PROTECTED]> wrote: > Reuse or not is not the point i think for this case > Because reuse is used when you rerender the complete repeater > but that is something they dont want to happen. They only want to rerender 1 > item (or something in the item) > But it is not that easy to get the component from that item,,
I was just thinking out loud so it might not make sense. I was thinking that we might be able to use the reuse strategy to determine what elements should be re-rendered. It might mean a bit of work, and probably even API breaks, so not something for 1.3 to do. "Iterator items = getItemReuseStrategy().getItems(itemFactory, models, getItems());", can be compared with the current children (right before removeAll is called), and some 'changed' property could be set on the new items so that they could later be picked up with a visitor that determines which elements should be re-rendered. I can imagine such an implementation to get pretty hairy quickly, but I think it is doable to provide such functionality transparently. Whether it is worth the effort in this stage I'm not sure. Users are welcome to propose though patches as well. Eelco
