Re: [Springframework-developer] ApplicationEventMulticaster

[<jue...@we...>]

Ross,
=20
We currently do such checks as follows throughout the framework:
- if the context can work with multiple beans of a type, detect by bean =
type
- if the context expects a single bean of that type, detect by bean name
=20
Detecting by name allows to define other beans of the same type, which =
will be ignored by the context. For example, the context-detected =
"applicationEventMulticaster" could delegate to backend =
ApplicationEventMulticasters, or some components could access their own =
ApplicationEventMulticaster beans without the context being involved.
=20
Therefore I'd like to keep it by name, as long as the context isn't =
supposed to work with multiple ApplicationEventMulticasters.
=20
Juergen
=20

________________________________

Von: spr...@li... im Auftrag =
von Mason, Ross
Gesendet: Sa 03.07.2004 08:36
An: spr...@li...
Betreff: [Springframework-developer] ApplicationEventMulticaster


Hi Juergen,
=20
Good work on the new event multicaster enhancements!=20
I noticed that you look in the container for a bean called =
'applicationEventMulticaster' to resolve the multicaster to use.  A =
small point, but why not just look for a bean of type =
ApplicationEventMulticaster? IMHO making it bean id dependent is =
superflous when the type can be used.  I've attached a minor enhancement =
to the AbstractContainerContext to remove the naming requirement for the =
event multicaster JIC :-)  I've also run all the tests without failures.
=20
Cheers,
=20
Ross
=20