the solution I implemented: redefining "methodmissing" in the classes
described by the resource
and pointing to a static general method that handles the redefined methods:
-----------------------------------------------------------
clazz.metaClass."methodMissing" = { name, args -> missMethod(delegate, name,
args) }
----------------------------------------------------------
the static missMethod picks up the translation of the method and invokes the
original method.now still a question: is using systematically "methodMissing" a significant performance penalty over adding a new method to the metaClass. ----- member of Grumpy Old Programmers -- View this message in context: http://groovy.329449.n5.nabble.com/aliasing-methods-tp5732316p5732339.html Sent from the Groovy Users mailing list archive at Nabble.com.
