-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> you can use the onActivate method in the following form:
>
> class MyPage { @Property String x;
>
> public onActivate(EventContext context) { if (context.getCount() >
> 0) { this.x = context.get(String.class, 0); } else { this.x =
> "default value"; } } }
>
> the "onActivate" event handler with the single EventContext
> parameter gets invoked in any case, regardless of the activation
> context parameter count (gets invoked with no activation context
> too!).
Thanks for pointing this out! Not quite as easy to read as an
'onActivate' method with an explicit parameter list, though.
Can someone point tell me the rationale for Tapestry calling all
onActivate() methods, and especially calling those with fewer
parameters *after* those with more parameters? Having them called in
reverse sequence would simplify initialization for me.
There are probably good reasons for doing it the way it is done, and I
would like to understand them ;-)
> nice to see you working with tapestry, i know your name from the
> german java scene and appreciate, that tapestry gets increasingly
> attention in germany ;)
;-)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+mEKoACgkQbmZsMyUPuXS8agCgyArTeRQn3WA6c1uFR90yqJIV
OkgAmgLo2dGzgD7kvjPpusFMC8CIFzjB
=CWN+
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
