Parameters not using setters?

2008-05-05 Thread Alexander Lamb
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

Re: Parameters not using setters?

2008-05-05 Thread Howard Lewis Ship
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

Re: Parameters not using setters?

2008-05-05 Thread Josh Canfield
You can use ComponentResources.isBound(paramname) to determine if the parameter has been set. Add it to your setupRender method. 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

Re: Parameters not using setters?

2008-05-05 Thread Alexander Lamb
So maybe it was in Tapestry 4... we migrated a rather large app so maybe I am just now discovering some side effects of the migration! Anyhow, I need to know when a parameter has changed. For the time being I do the test in setupRender. Someone suggested ComponentResources.isBound(paramname)