You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by "Rhodes, Phillip C." <Ph...@alcoa.com> on 2003/11/19 20:48:11 UTC
purpose of abstract set/get methods?
I see in some examples that one will declare setters and getters abstract for simple properties in a component or page.
What is the advantage of not implementing the 1 line of code to do the actual set/get (and declare the instance variable)?
Is this required for persistent properties? I thought all one had to do for persistent properties was to declare it in the page or property spec...
Thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: purpose of abstract set/get methods?
Posted by Jeff Emminger <je...@jeffemminger.com>.
actually I was looking for the whole thread...try this:
http://www.caddr.com/macho/archives/tapestry-users/2003-11/2210.html
Jeff Emminger wrote:
> this might help too:
>
> http://article.gmane.org/gmane.comp.java.tapestry.user/4804
>
>
>
> Rhodes, Phillip C. wrote:
>
>> I see in some examples that one will declare setters and getters
>> abstract for simple properties in a component or page.
>>
>> What is the advantage of not implementing the 1 line of code to do the
>> actual set/get (and declare the instance variable)?
>> Is this required for persistent properties? I thought all one had to
>> do for persistent properties was to declare it in the page or property
>> spec...
>>
>>
>> Thanks.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: purpose of abstract set/get methods?
Posted by Jeff Emminger <je...@jeffemminger.com>.
this might help too:
http://article.gmane.org/gmane.comp.java.tapestry.user/4804
Rhodes, Phillip C. wrote:
> I see in some examples that one will declare setters and getters abstract for simple properties in a component or page.
>
> What is the advantage of not implementing the 1 line of code to do the actual set/get (and declare the instance variable)?
> Is this required for persistent properties? I thought all one had to do for persistent properties was to declare it in the page or property spec...
>
>
> Thanks.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org