I'm afraid you are mistaken; this aspect of parameter handling has not
changed over the lifetime of T5. Tapestry has never used accessor
methods to set parameter values. it *is* perfectly valid for your
code to implement an accessor method around a parameter-bound field,
and for code to invoke the method ... but Tapestry doesn't access it
that way.
On Mon, May 5, 2008 at 8:26 AM, Alexander Lamb
<[EMAIL PROTECTED]> wrote:
> Hello list,
>
> Some time ago (5.0.?) when I had a component with a parameter, I could
> implement a set method which would do some additional "cleaning up".
>
> For example:
>
> @Parameter(required = true)
> private RegistryCenter _selectedRegistryCenter;
>
> public void setSelectedRegistryCenter(RegistryCenter value) {
> _role = null;
> _selectedRegistryCenter = value;
> }
>
> Now, it seems like in the last version(s) of Tapestry, parameter setting is
> not using the set methods!?!
>
> If so (which broke my app BTW), what can I do to recuperate this kind of
> behavior (e.g. do something when a parameter is set).
>
> Thanks,
>
> Alex
> --
> Alexander Lamb
> Founding Associate
> RODANOTECH Sàrl
>
> 4 ch. de la Tour de Champel
> 1206 Geneva
> Switzerland
>
> Tel: 022 347 77 37
> Fax: 022 347 77 38
>
> http://www.rodanotech.ch
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
