|
From: Juergen H. <ju...@in...> - 2005-06-02 20:05:37
|
Hi Mike, That should actually be considered a bug in Spring. Existing bean instances passed into AutowireCapableBeanFactory methods should not be considered as shared instances but rather as independent instances, outside Spring's lifecycle management. There is no need to track dependencies for such bean instances. Hence, I've changed AbstractAutowireCapableBeanFactory to create prototype bean definitions for its temporary needs there, avoiding the dependency tracking that would kick in for singletons. This will be available in tomorrow's nightly snapshot (in about 26 hours) and make it into the upcoming Spring 1.2.2. Feel free to give it an early try! Regarding private/public/protected bean visibility: Admittedly, this doesn't have high priority at this point of time. We mainly recommend to use inner bean definitions for beans that you don't want to expose at all. Explicit control of the public visibility vs the internal visibility of beans would be nice, of course, but is not entirely trivial to solve for the general case (for example, across multiple context definition files). I guess we'll target this for Spring 1.3, given that there's a major adopter waiting for it :-) Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Mike Cannon-Brookes Sent: Thursday, June 02, 2005 9:36 PM To: Spring Developer Subject: [Springframework-developer] Creating Memory Leaks with Spring Hey guys, One of our dev's found this 'leak' (after days of tracking down a leak) and wrote it up: http://confluence.atlassian.com/display/DEV/Creating+Memory+Leaks+with+Sprin g Are we doing things wrong? Is the new factory workaround the 'right' way to do this? Are we the only ones autowiring so many beans that we notice the memory effects? Any ETA on private/public/protected bean protections? (ok, this one has nothing to do with the leaks but I thought I'd throw it in anyway ;)) Cheers, Mike -- ATLASSIAN - http://www.atlassian.com ------------------------------------------------------- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=fad-ysdn-ostg-q22005 _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |