|
From: Rod J. <ro...@in...> - 2004-08-21 12:39:24
|
Such visibility options make sense IMO. However, I would prefer that this was considered for 1.2 rather than 1.1 final. As with abstract definitions, enumeration methods on ListableBeanFactory shouldn't return non-public beans. Btw, inner beans are a good alternative: for example, instead of the xxxx/xxxTarget combination for ProxyFactoryBean, just xxxx, with the target an anonymous inner bean. _____ From: spr...@li... [mailto:spr...@li...] On Behalf Of jbetancourt Sent: 21 August 2004 12:12 To: spr...@li... Subject: [Springframework-developer] declaritive context visibility of bean definitions? Just had a thought while reading the 'explicity abstract' message. Would it make sense to have the ability to make bean definitions 'private', that is local only to other beans in the same context, and the default is 'public'? I can't think of a use-case for this or if it is already possible in current Spring core. <bean ...... access="public" /> or <bean ....... public="false" /> Just a thought. |