this is how free I felt:
https://issues.apache.org/jira/browse/WICKET-2321
I'd be looking forward for that especially in the context of Ajax and
keeping control over JavaScript objects on the browser side. Like
components that induce the instation of JavaScript objects in the
Browser.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
--
View this message in context:
http://www.nabble.com/Component-lifecycle-question-tp23913399p23961642.html
Sent from the Wicket - User mailing
://www.nabble.com/Component-lifecycle-question-tp23913399p23961642.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail
On Sun, Jun 7, 2009 at 10:40 AM, Martin Funkmafulaf...@googlemail.com wrote:
Hi list,
in short:
Why is there no Component#onRemove() method?
because no one asked for it. feel free to create a jira issue with the request.
-igor
I see that there is Component#onDetach() which is called by
Hi list,
in short:
Why is there no Component#onRemove() method?
I see that there is Component#onDetach() which is called by
Component#remove(), so it might be a good candidate.
But onDetach is also called at the end of every RequestCycle.
I have things that I want to get done when a
Hi list,
I want to create the UI of a MarkupContainer after it has been added to
the component hierarchy, because I need to get to the Page for
information needed in constructing the UI.
MarkupContainer.onBeforeRender() just doesn't smell right and passing
the Page as an argument in the
