15 messages in org.codehaus.groovy.userRe: [groovy-user] Setter overloading ...
FromSent OnAttachments
Marc PalmerJun 4, 2008 7:08 am 
Jochen TheodorouJun 4, 2008 9:01 am 
Luke DaleyJun 4, 2008 3:44 pm 
Marc PalmerJun 5, 2008 2:57 am 
Jochen TheodorouJun 5, 2008 3:32 am 
Jochen TheodorouJun 5, 2008 3:43 am 
Luke DaleyJun 5, 2008 4:51 pm 
Danno FerrinJun 5, 2008 6:24 pm 
Jochen TheodorouJun 5, 2008 7:12 pm 
Luke DaleyJun 5, 2008 7:52 pm 
Luke DaleyJun 5, 2008 8:48 pm 
Michael S. JessopJun 5, 2008 9:49 pm 
Jochen TheodorouJun 6, 2008 4:03 am 
Danno FerrinJun 6, 2008 5:25 am 
Danno FerrinJun 6, 2008 5:28 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [groovy-user] Setter overloading - should it work?Actions...
From:Danno Ferrin (dann@shemnon.com)
Date:Jun 6, 2008 5:25:13 am
List:org.codehaus.groovy.user

On Thu, Jun 5, 2008 at 9:49 PM, Luke Daley <ld@ldaley.com> wrote:

On 06/06/2008, at 11:25 AM, Danno Ferrin wrote:

The default MetaClass infrastructure inside of Groovy asks for the

BeanInfo to set it's getter and setter methods, so the JavaBeans infrastructure is used direcly by Groovy.

Is this a _requirement_ though? (asking, not implying it isn't)

If we are going to say that x.y means use the JavaBeans property y, then yes it is a _requirement_. How else would we find out that the bean author has set the method 'quackQuack(int)' to be the setter for property y?