Community
Participate
Working Groups
Discovered while discussing something with Ramnivas. There are some issue with extending the GenericInterfaceDrivenDependencyInjectionAspect. By extending it and including spring-aspects.jar on your inpath it should work without introducing a readResolve into any user/consuming code. But it doesn't - once extended the next weave should require the readResolve to be woven, which should be possible due to it being accessible on the inpath.
unsetting the target field which is currently set for something already released