Yeah, I mean I think you covered that very well. I just don't think
in general a managed bean has any reason to access the container,
since you really should be able to set up your beans in such a way
that CS can handle your dependencies for you!
On Mar 9, 2006, at 8:13 PM, Sean Corfield wrote:
On 3/9/06, Chris Scott <[EMAIL PROTECTED]> wrote:
Before we all get too crazy trying to figure out how to have an
object
become auto wired with the bean factory, ColdSpring already
provides a
ServiceLocator type utility to manage the location of the bean
factory for
you, in a provided scope.
Ah, very cool... and it takes the name of the scope?
Still, it does kind of emphasize the "don't have managed beans depend
on the container" kinda thing...
--
Sean A Corfield -- http://corfield.org/
Got frameworks?
"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood
