[jira] [Commented] (GROOVY-3867) Allow methodMissing/propertyMissing to be defined through category

["Ruben Laguna (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GROOVY-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16283252#comment-16283252 ] 

Ruben Laguna commented on GROOVY-3867:
--------------------------------------

I've opened a new issue GROOVY-8408 from a conversation with [~blackdrag] in the [http://markmail.org/message/xlj74kawyayspnzv?q=list:org%2Eapache%2Egroovy%2Eusers+category+category] which is related to this issue. (invokeMethod instead of missingMethod) 


> Allow methodMissing/propertyMissing to be defined through category
> ------------------------------------------------------------------
>
>                 Key: GROOVY-3867
>                 URL: https://issues.apache.org/jira/browse/GROOVY-3867
>             Project: Groovy
>          Issue Type: Improvement
>          Components: groovy-runtime
>    Affects Versions: 1.6.5
>            Reporter: Kohsuke Kawaguchi
>         Attachments: categoryAndMissingMethodFailingTest.patch
>
>
> When integrating a library defined by a 3rd party into Groovy, it's often convenient to be able to define missing method/property receiver. Since I can't modify the library directly, it would be great if this can be achieved via category.
> In the current MetaClassImpl implementation, category isn't searched for a missing method/property receiver.
> Note that the generic "Object get(String name)" serves as a replacement for propertyMissing, but there's nothing like that for methods. Plus the get method isn't invoked for "foo.someMethod(...)" even though it works for "(foo.someMethod)(...)" due to the difference in the property look up and method invocation handling.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)