DO NOT REPLY [Bug 38929] - [configuration] Support event listeners for configurations

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38929>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38929





------- Additional Comments From joerg.schaible@gmx.de  2006-03-13 08:53 -------
Nice, I thought about this also for some time. The listener/monitor concept can
be applied for other events:
- property not found (instead of ignoring or throwing an exception - the
registered listener can do this then - and we can get rid of the method in
AbstractConfiguration and all this special handling)

setProperty-Problem: Maybe we have a bulkChangeStart/bulkChangeEnd event, so
that a listener implementation may optimize the configurationChanged events
inbetween ?

And yes, reload should raise an event. It is up to the listener implementation
to do soemthing useful about it. And it could also make usage of the bulk change.

- J�rg

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org