Dave Newton 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.

I have no idea.  I was just throwing out random theories of what might
have been causing this guy grief.  Since he was getting a valid value
for this attribute ("[]" although he was expecting "['TEST1', 'TEST2']")
I think I'm wrong here.  Sounds like you *know* that I'm wrong here, so
I'll withdraw the idea as bone-headed :-)  (But if the action class is
somehow hidden in his call stack by a proxy class through AOP or
something, maybe?)

-Dale

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@stru...
For additional commands, e-mail: dev-help@stru...