Hello everybody.
It is indeed as Robert is saying. And after changing the code, it works
Component component = page.get(pageRelativeComponentPath);
// See {@link
//
BookmarkableListenerInterfaceRequestTarget#processEvents(RequestCycle)}
// We make have to try to look for the component twice, if we hit
the
// same condition.
if (component == null) {
page.prepareForRender(false);
component = page.get(pageRelativeComponentPath);
//Component no longer null
....
Looking at "BookmarkableListenerInterfaceRequestTarget#processEvents" we
find the comment:
"this is quite a hack to get components in repeater work. But it still can
fail if the repeater is a paging one or on every render it will generate new
index for the items..."
I was trying to implement a comment system for articles. The stateless ajax
buttons would be reply buttons for comments that can span multi levels. I
can't feel confident that the comment hierarchy will not change by the time
the user clicks reply. Currently I'm thinking of moving the reply as a
behaviour outside the repeater, and use JQuery to pass the comment id to
that behaviour so I can know to which comment the user is replying.
Thanks everybody.
-----
http://balamaci.wordpress.com
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Stateless-Wicket-and-Ajax-tp3348266p3352490.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
