Re: [Springframework-developer] Internal use of deprecated methods

[Juergen H. <ju...@in...>]

Good point: those should indeed use the new methods. I've just fixed all
such uses of beanNamesIncludingAncestors and related methods.

Juergen


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf
Of Erwin Vervaet
Sent: Saturday, June 18, 2005 6:37 PM
To: spr...@li...
Subject: [Springframework-developer] Internal use of deprecated methods


I was wondering whether or not the framework should use it's own deprecated
methods. For instance, on line 402 of ProxyFactoryBean we find:

String[] globalAdvisorNames =
BeanFactoryUtils.beanNamesIncludingAncestors(beanFactory, Advisor.class);

And the "beanNamesIncludingAncestors" method of BeanFactoryUtils is
deprecated. We could rewrite this using the new prefered method:

String[] globalAdvisorNames =
BeanFactoryUtils.beanNamesForTypeIncludingAncestors(beanFactory,
Advisor.class);

Is there a particular reason to keep using the old deprecated method?

Erwin Vervaet
erw...@er...



-------------------------------------------------------
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