i guess the problem here is the fact that the index of the list is not a stable id. what about using a map and keying off a counter. you can also sort the map on the counter so the order will be just like a list. -Igor
On 12/14/05, Laurent PETIT <[EMAIL PROTECTED]> wrote:
I'm not sure we're talking
I'm not sure we're talking about the same thing. But as I understand
what you suggest: if I rebuild the models & the Items, then I'll loose
the inputs the user has already done on the Form Components. And if I
keep the Items but rebuild the models, then there is a risk of having
an Item, initialize
why not just rebuild the models if one or more are deleted?-IgorOn 12/13/05, Laurent PETIT <[EMAIL PROTECTED]
> wrote:Igor,thanks for your answer.On 12/14/05, Igor Vaynberg <
[EMAIL PROTECTED]> wrote:> as far as the models go, maybe what you can do is make a "detachable" model> that instead of the
Igor,
thanks for your answer.
On 12/14/05, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> as far as the models go, maybe what you can do is make a "detachable" model
> that instead of the identity keeps the index of the list. so when you call
> getobject() on it it will retrieve that object from the
On 12/13/05, Laurent PETIT <[EMAIL PROTECTED]> wrote:
Hello Igor,On 12/13/05, Igor Vaynberg <[EMAIL PROTECTED]> wrote:> I did not put this strategy [ReuseIfModelObjectsEqualStrategy] in extensions on purpose.
> The reason being is that this can really get you in trouble when dealing with detachable
Hello Igor,
On 12/13/05, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> I did not put this strategy [ReuseIfModelObjectsEqualStrategy] in extensions
> on purpose.
> The reason being is that this can really get you in trouble when dealing with
> detachable models.
> Imagine changing a page and having
I did not put this strategy in extensions on purpose. The reason being is
that this can really get you in trouble when dealing with detachable
models.
Imagine changing a page and having all the model's from last page load as
well as all the models on this page. The idea behind ifmodelequals was
Hello,
> I do not undestand the question either. Maybe you can provide some code
> pointers and rephrase it. Also maybe a unit test that displays the problem
> so that i can clearly see what it is.
Yes I'll do so, asap.
cu,
--
laurent
---
Th
On 12/13/05, Christian Essl <[EMAIL PROTECTED]> wrote:
ReuseIfModelObjectsEqualStrategy is a good idea (much better thanextending ListDataProvider and Model). Maybe Igor could take it intoextensions.I did not put this strategy in extensions on purpose. The reason being is that this can really get y
Hi Laurent,
Thanks for the good example of an indeed complex form.
Sorry I can't answer your question or realy give better advice. But some
comments:
Then I used the DataView of wicket-extensions. I only had to write a
custom ReuseIfModelObjectsEqualStrategy in order to make it work ( I
thin
Hello,
I've been working during my free time on a wicket port of the
struts-nested sample example. (For those who don't know what struts
nested is, it is, for the struts community, the jsp library that
allows developers to do complex nesting levels of form models, with
many levels editable at the
11 matches
Mail list logo
