Is anyone aware of a current, valid use-case of allowing the same
listener class to be registered multiple times for the same event? I
know we have many "multi-faceted listeners that listen for many events.
Thats not what I mean. I mean, is there ever a time anyone can think of
when something lik
I am not a fan of this. For a number of reasons.
First this means added complexity to manage the list of listeners in
regards to (1) not over-writing any explicitly registered listeners and
(b) not duplicating listeners.
Second keep in mind that the hibernate3.jar from the release
distribution
I would favor such model ie. an automatic event registration when the lib is in
the classpath.
We could generalize that actually to let any lib to register its event
listeners (maybe something a la service locator).
Today Search and Validator have a specific hook in Core.
On 11 sept. 2010, at 09
