|
From: Rob H. <ro...@ca...> - 2004-07-31 14:36:07
|
I think that would be a good idea, be a bit more explicit. Colin Sampaleanu wrote: > Colin Sampaleanu wrote: > >> Rob Harrop wrote: >> >>> Reading through the 1.1 docs it says that a parent bean can never >>> be accessed directly in an app either through <ref> or getBean() yet >>> I was able to do both. Is this an error in the doc or the code? >>> >>> Rob >> >> >> >> This is prefaced with the text 'In the case that the parent >> definition does not specify a class' before the sample... >> >> If it has a class, it's usable as its own bean, and in fact you need >> to make it lazy-init=true or singleton=true to stop the factory from >> pre-instantiating it. I need to update the docs to specifically >> mention that. > > > We could consider an 'abstract' attribute actually, to stop a bean > from ever being instantiated... > > Colin > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by OSTG. Have you noticed the changes on > Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, > one more big change to announce. We are now OSTG- Open Source Technology > Group. Come see the changes on the new OSTG site. www.ostg.com > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |