I don't think that is right. But if you are using AOP that "final"
there could cause problems, depending on the implementation.
musahcy
On Thu, Mar 12, 2009 at 2:42 PM, Dave Newton <newton.d...@yahoo.com> wrote:
> Dale Newfield wrote:
>>>
>>> public final List<String> getPayPlanTypes() {
>>> return payPlanTypes;
>>> }
>>>
>>> public final void setPayPlanTypes(List<String> payPlanTypes) {
>>> this.payPlanTypes = payPlanTypes;
>>> }
>>
>> I recognize that "final" for methods is an attempt to make this
>> not-over-ridable, but I wonder if that's not causing grief. (Maybe the
>> compiler is in-lining them, but that means it's not visible in the
>> reflection api that's used to find the appropriate attributes?)
>
> ?!
>
> Is that true? I've never seen or heard anything like that before; that seems
> like it would completely break everything JavaBean-ish ever.
>
> Dave
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
> For additional commands, e-mail: dev-h...@struts.apache.org
>
>
--
"Hey you! Would you help me to carry the stone?" Pink Floyd
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
