Igor,
Thanks for this new feature!
Just one question/remark... the JavaDoc of onBeforeRender states
* Because this method is responsible for cascading {...@link
#onBeforeRender()} call to
* children it is strongly recommended that super call is made at the
end of the override.
Is this also
onInitialize() is called only once, like the javadoc says.
-igor
On Mon, Jul 12, 2010 at 10:58 PM, Ernesto Reinaldo Barreiro
reier...@gmail.com wrote:
Igor,
Thanks for this new feature!
Just one question/remark... the JavaDoc of onBeforeRender states
* Because this method is responsible
for rendering event.
Looking forward for 1.4.10
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/new-feature-in-trunk-and-branch-Component-onInitialize-tp2286924p2287133.html
Sent from the Wicket - User mailing list archive at Nabble.com
/new-feature-in-trunk-and-branch-Component-onInitialize-tp2286924p2287133.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional
Nice, I have one or two places where onInitialize would make more sense than
onBeforeRender. Thanks for the update!
One question, does it matter where in the override we call super#onInitialize
(beginning or end)?
i think in most cases it would make sense to call super first, just
like the constructor.
-igor
On Tue, Jul 13, 2010 at 8:35 AM, Josh Glassman josh...@gmail.com wrote:
Nice, I have one or two places where onInitialize would make more sense than
onBeforeRender. Thanks for the update!
One
.nabble.com/new-feature-in-trunk-and-branch-Component-onInitialize-tp2286924p2287133.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional
there have been a lot of threads over the years about having some
place to initialize components other than constructors. there are a
few problems with constructors, such as not being able to call
getPage() or non-final methods. historically we have refused to
implement this because we have
Very cool. Thanks, Wicket Team!
On Mon, Jul 12, 2010 at 10:09 PM, Igor Vaynberg igor.vaynb...@gmail.com wrote:
there have been a lot of threads over the years about having some
place to initialize components other than constructors. there are a
few problems with constructors, such as not
very good feature,thanks!!
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/new-feature-in-trunk-and-branch-Component-onInitialize-tp2286924p2286961.html
Sent from the Wicket - User mailing list archive at Nabble.com
thanks you all
On Tue, Jul 13, 2010 at 12:19 AM, vineetsemwal
vineetsemwal1...@gmail.comwrote:
very good feature,thanks!!
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/new-feature-in-trunk-and-branch-Component-onInitialize-tp2286924p2286961.html
Sent from
11 matches
Mail list logo
