tag:blogger.com,1999:blog-3339316202894508517.post4542956456020685224..comments2009-05-13T15:42:49.889-07:00Brian Duffhttp://www.blogger.com/profile/15591692569924908268noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3339316202894508517.post-86145090941198851712007-11-16T15:10:00.000-08:002007-11-16T15:10:00.000-08:00What a clever use of the ForwardingList! The authors' original intent was really to improve abstractions and eliminate repetition in the Collections library, it's nice to see it has other practical applications.<BR/><BR/>You briefly mention enabling this only for debug environments. I haven't used Guice yet, and I know just a little bit about bytecode injection, but I keep thinking how one might use those to automatically provide this behavior to concrete list implementations, providing an easy way to track down such exceptions without recompiling code.<BR/><BR/>Tangentially, here in Google Santa Monica, our Design Patterns reading group just finished discussing Decorator. Since people tend to think of patterns in their, shall we say, prototypical environment (GUI components, Java IO library), this helped reinforce the value of discussing patterns in non-standard environments.Robert Konigsberghttp://www.blogger.com/profile/04616226121996611123noreply@blogger.comtag:blogger.com,1999:blog-3339316202894508517.post-55546442570996598032007-11-16T00:59:00.000-08:002007-11-16T00:59:00.000-08:00Something I've experienced a few times is an assumption that ConcurrentModificationException automatically means you have a problem with threads.<BR/><BR/>This article explains how you can experience the ConcurrentModificationException in a single thread:<BR/><BR/>http://www.java2s.com/Tutorial/Java/0140__Collections/ConcurrentModificationException.htmAnonymousnoreply@blogger.com