tag:blogger.com,1999:blog-6178209.post113349793605755245..comments2009-02-23T13:33:35.221-06:00Igorhttp://www.blogger.com/profile/12832903167357753682noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6178209.post-1133960099585468232005-12-07T06:54:00.000-06:002005-12-07T06:54:00.000-06:00For example, having common Root superclass (referring to Fowler's pattern...) which performs autowiring in its constructor.<BR/><BR/>However, for this thing to work properly, you need some dirty things, e.g. static fields referring to Spring bean factory. So it would be somewhat similar to "ServiceManager" but having all dirty things hidden inside superclass.<BR/><BR/>Also, some bytecode instrumentation for constructors comes in mind...snekovalnoreply@blogger.comtag:blogger.com,1999:blog-6178209.post-1133512245021077632005-12-02T02:30:00.000-06:002005-12-02T02:30:00.000-06:00Good stuff. I've been thinking about this sort of thing ever since I started using Spring but I don't have a clear resolution yet. I'm inclined to use Service Locators or parameters but I haven't really pushed this far enough to have a really strong opinion on this yet.Jason Yiphttp://www.blogger.com/profile/08286768587936088382noreply@blogger.com