define reliably. markupid should never be used by anything other then
wicket - we have never guaranteed its stability. did you ever create the rfe
to have the id migrated when components are replaced? that is the only
usecase i can think of where we need to worry about the id being stable so
that
* Igor Vaynberg:
define reliably. markupid should never be used by anything
other then wicket - we have never guaranteed its stability. did
you ever create the rfe to have the id migrated when components
are replaced? that is the only usecase i can think of where we
need to worry
hrm, i dont see how this can happen.
once an id is created for a component that component keeps it for its entire
lifetime - it is cached in the component's metadata.
the counter is also nontransient so it keeps its value as long as the page
is alive.
can you recreate it using wicket tester?
Hi,
I notice after upgrading from wicket 1.2 to current wicket-1.x
that replaceWith() combined with an AjaxRequestTarget does not
work anymore. I recall that you added smart markup ids with auto
increments.
So what I propose is to add to the migrate-1.3 wiki page the
following,
our replace methods should migrate the id imho. please add an rfe.
-igor
On 11/26/06, Jean-Baptiste Quenot [EMAIL PROTECTED] wrote:
Hi,
I notice after upgrading from wicket 1.2 to current wicket-1.x
that replaceWith() combined with an AjaxRequestTarget does not
work anymore. I
