You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Ruben Laguna (JIRA)" <ji...@apache.org> on 2017/12/08 09:20:00 UTC

[jira] [Created] (GROOVY-8408) invokeMethod cannot be set through category

Ruben Laguna created GROOVY-8408:
------------------------------------

             Summary: invokeMethod cannot be set  through category
                 Key: GROOVY-8408
                 URL: https://issues.apache.org/jira/browse/GROOVY-8408
             Project: Groovy
          Issue Type: Bug
    Affects Versions: 2.6.0-alpha-2, 2.4.13, 3.x, 2.5.x
            Reporter: Ruben Laguna
         Attachments: categoryMissingMethod.groovy

In the Groovy in Action book, chapter 8.4.5 says 

{quote}Category method names can well take the form of property accessors (pretending property access), operator methods, and GroovyObject methods. MOP hook methods cannot be added through a category class. This is a restriction as of Groovy 2.4. The feature may become available in later versions.{quote}

It interpreted this as meaning that I can add GroovyMethods (getProperty,
getMetaClass, invokeMethod , setMetaClass and setProperty)  to a class using categories but not
methodMissing or propertyMissing (which I think they call MOP hook methods in the GINA book).

But when I tried to add invokeMethod using a category the change has no effect, adding missingMethod does not work either see attachement. 

I see that methodsMissing/ propertyMissing via category was probably never supported noted in GROOVY-3867. But the Groovy in Action paragraph makes me think that invokeMethod et al were supported at some point. 





[http://markmail.org/message/xlj74kawyayspnzv?q=list:org%2Eapache%2Egroovy%2Eusers+category+category]




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