commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 33926] - [configuration] The Iterator returned by getKeys() should support remove()
Date Wed, 06 Apr 2005 17:45:21 GMT
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 ebourg@apache.org  2005-04-06 19:45 -------
(In reply to comment #1)
> 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.

How do plan to implement that ? If the configuration is based on a Collection
like BaseConfiguration, you'll get a ConcurrentModificationException on calling
clearProperty from the Iterator. What about firing an event in the remove()
method instead of calling clearProperty() ?


-- 
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


Mime
View raw message