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-unsubscribe@stru...
For additional commands, e-mail: dev-help@stru...