|
From: Rob H. <ro...@ca...> - 2004-12-17 12:42:53
|
All, I am planning to add to an additional proxy implementation to Spring to solve some of the problems we are experiencing with other approaches and to allow for additional optimizations and advice types to be added in the most efficient way. Currently, I'm looking at two separate approaches - Java-based using Janino and Bytecode-based using SERP. The Java-based approach should be quite simple to create and could be coupled with Velocity to externalize much of the boilerplate code needed for the creation of proxy classes. Alternatively we could add a simple abstraction layer on top of Janino, a la .NET CodeDOM (good idea James). The bytecode approach is much more complex and will be harder to debug but it would probably allow for absolute raw performance. I am comfortable with either approach although I think that Janino would be ideal for our purposes. Your thoughts? Rob |