Ja, I have (and require) the "100% solution". However, I was mean enough not to tell of a joker I have: all my Spring IoC config is being generated thru XSLT from another generic format, thus I can cover the redundancy using the XSL template in combination with XSL parameters.
So, first hand, I will most probably stick to the injection method - still having the problem that I have to use constructor instead of setter due to "calling order" problems...
VERY big thanks to you! I'll stick to that AOP stuff however.
Just as a sidenode: in German Wikipedia, the author(s) tell that AOP might also be suitable to replace existing event mechanismens by using AOP in order to have less event-interface dependnencies etc. As we are creating a project depending on Human Interface Decives (HID, e.g. joystick), using AOP for "doing events" sounds interesting. I'll try further ;-)
Thanks and regards,