You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2005/03/09 19:55:01 UTC
DO NOT REPLY [Bug 33926] -
[configuration] The Iterator returned by getKeys() should support remove()
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=33926>.
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=33926
------- Additional Comments From oliver.heger@t-online.de 2005-03-09 19:55 -------
Not a big blocker I would say.
Well, if this feature is desired, a possible solution would be to let
AbstractConfiguration return a special (non public) ConfigurationIterator, which
wraps an iterator obtained from a concrete sub class. This special iterator
implementation could store a reference to the associated Configuration object
and route the remove() method to this configuration's clearProperty() method.
I think, it is important that the removal is done by the clearProperty() method
itself (so I am not too content that remove is supported by some Configuration
classes directly) because there might be other actions associated with this. One
example would be observable configurations where a removal of a property should
cause an event to be fired.
--
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