Re: [Springframework-developer] declaritive context visibility of bean definitions?

[Martin K. <Mar...@St...>]

There is also an thread within the new forum. Maybe someone should
take a look. There were some issues raised about the visibility, =
extendability
of application contexts.
  ----- Original Message -----=20
  From: Rod Johnson=20
  To: spr...@li...=20
  Sent: Saturday, August 21, 2004 2:38 PM
  Subject: RE: [Springframework-developer] declaritive context =
visibility of bean definitions?


  Such visibility options make sense IMO. However, I would prefer that =
this was considered for 1.2 rather than 1.1 final.=20

  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.  =20

  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=3D"public" />

  or=20

  <bean  .......   public=3D"false" />



  Just a thought.