Comments on: Broken JavaBeans due to pass-by-reference expectation http://steep.blogsome.com/2006/07/10/broken-javabeans-due-to-pass-by-reference-expectation/ Hayden Steep's development obstacle course. (Java, JEE, and beyond) Wed, 16 Dec 2009 10:46:41 +0000 http://wordpress.org/?v=1.5.1-alpha by: Carsten Saager http://steep.blogsome.com/2006/07/10/broken-javabeans-due-to-pass-by-reference-expectation/#comment-3 Tue, 11 Jul 2006 16:49:35 +0100 http://steep.blogsome.com/2006/07/10/broken-javabeans-due-to-pass-by-reference-expectation/#comment-3 When returning read-only lists it is always wise to pass them through Collections.unmodifiableList(); of course this is only really safe if all object in the list are immutable, too. Most of the time an iterator will do, so nobody is tempted to call add on it. When I want to provide "property-style" access I define a function list1() or whatever the name of the (pseudo)-member is. The effort to do so is not negligable and most of the time all but justified. When returning read-only lists it is always wise to pass them through Collections.unmodifiableList(); of course this is only really safe if all object in the list are immutable, too.

Most of the time an iterator will do, so nobody is tempted to call add on it.

When I want to provide “property-style” access I define a function list1() or whatever the name of the (pseudo)-member is. The effort to do so is not negligable and most of the time all but justified.

]]>