|
From: Juergen H. <ju...@in...> - 2005-07-07 11:02:33
|
Hi Mark, I haven't given much thought to this yet. The question is whether there are enough good use cases for this. After all, there's always the option to override autowiring at the level of the bean that receives autowiring: You can always explicitly specify references for specific properties of constructor arguments there, which will override any autowiring that you configured for that bean. In general, I agree with Seth that inner bean definitions can get you quite far as well, in particular regarding proxy vs target. We're illustrating that configuration style in JPetStore, for example. Autowiring will always only consider the outer bean (the proxy) in such a scenario, never the inner bean (the target). Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...] On Behalf Of Mark Vickers Sent: Wednesday, July 06, 2005 9:06 PM To: 'spr...@li...' Subject: [Springframework-developer] autowiring exclusion attribute Juergen et al, I've added a patch which addresses SPR-626 (autowiring exclusion attribute) http://opensource.atlassian.com/projects/spring/browse/SPR-626 Any chance of this making it into 1.3? A quick yea or nay would be appreciated - the presence/absence of this feature will greatly impact our development practices. Regards, Mark ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |