On Mon, May 5, 2008 at 1:03 AM, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > On Fri, May 2, 2008 at 8:45 AM, James Carman <[EMAIL PROTECTED]> wrote: > Anything AOP would complicate our building process and would mean > additional dependencies. I wouldn't be crazy about that. Also, the > ideal case would be that you could just extend the session and provide > your properties without having to even know about the dirty call in > setters. There should be simpler solutions than introducing AOP and/ > or annotations.
Again, this would be an optional module of course. And, adding AspectJ to the build process in maven is simple. It's just another build plugin. > > Can't we create create a proxy object for the session right after it > is created that adds calling dirty() to the setters it finds? Maybe > optional? That's a thought. I usually end up adding "session data" objects for each of my sub-modules. So, my main session has getters like getModule1Data(), getModule2Data(), etc. So, the proxy would have to be smart enough to create proxies to the submodule data also.
