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 ajax works.
-igor
On 12/7/06, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
* Igor Vaynberg:
> our replace methods should migrate the id imho. please add an rfe.
Back to this. Your change to the generation of markup ids in
branch 1.x does not work when a Page is restored from the session:
the auto-increment id returns 0.
The usecase is this:
MyPage has an embedded Form. And in this Form I do:
protected void onSubmit() {
MyPage p = (MyPage) findParent(MyPage.class);
Component c = p.get("someComponent");
System.out.println(c.getMarkupId()); // prints
"someComponent0"
}}
When reverting the markup id generation to the one in Wicket
1.2.3, markup ids work reliably.
Are you able to reproduce that? Are you using branch 1.x? Maybe
I should switch to trunk...
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
