Proxy-o-Matic lets you create dynamic proxies fast and in an homogeneous way
Proxy-o-Matic lets you create dynamic proxies fast and in an homogeneous way. Groovy has the option to create proxy implementations of interfaces, abstract classes and even concrete classes based on closures and maps. You can see them as a poor man's version of anonymous inner classes, but they are not an exact replacement as you can't qualify method calls with this nor super.
Proxies created with Proxy-o-Matic also suffer from the this/super problem but they add a couple of features that the standard proxy creation mechanism doesn't offer:
Here are a couple of examples that show how to use Proxy-o-Matic
Credit must be given when credit is due, in this case Proxy-o-Matic emerged from an idea Alex Tkachman pitched at the Groovy-dev mailing list, thanks Alex for the marvelous idea of a Proxy builder DSL.
Andres Almiray [aalmiray at users dot sourceforge dot net]
Just drop proxyomatic-<version>.jar into $GROOVY_HOME/lib or ~/.groovy/lib and your done.
Have the latest stable version of Groovy installed, that's all baby!
Using Proxy-o-Matic is pretty straight forward: call any of ProxyOMatic's proxy() methods. To achieve a DSL like usage remember to import statically
ProxyOMatic.proxy. Proxy-o-Matic can only create proxies from interfaces for the time being, abstract/concrete classes will be supported in a following version. These are the method signatures you would need to work with
where source can be any of [Closure, Map, Expando]
Another thing to consider is that given the nature of closures in Groovy the following would be treated as equivalent definitions:
So please avoid using the default parameter and always qualify the number of parameters a closure must have.
Please contact the team members by e-mail.