Ed,
Thank you so much for the reply. Could you please send me the link to the
working example. I would like to compare with the one I have.
Btw, thanks for pointing out the improper usage of table fragment as
panel. I have modified to div
Appreciate your help in this regard.
J.
--
View this
/form
/body
/html
Thanks
J
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Panel-re-rendered-twice-when-the-data-is-pulled-in-tp2268924p2268924.html
Sent from the Wicket - User mailing list archive at Nabble.com
.nabble.com/Panel-re-rendered-twice-when-the-data-is-pulled-in-tp2268924p2268924.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional
Ed,
Thanks for your reply. I already tried this. But still the problem exists.
:(
setResponsePage(getPage(this)) seems to be the work around for this issue.
But the problem is, the other inputfields that have values on this page are
lost when the panel is re-rendered.
I am not sure how to
Hmm, I took a working example that replaces a panel using an AJAX link
and altered the HTML to match what you have and, hey presto, after
clicking the link I have two versions of the panel content. Reload
and I have one again.
I don't have the code in front of me, but I'll take a look again