I really don't have a deep passion about this issue, but I would just like to register the opinion that this often triggers an avalanche of noise. Once you include the add method, someone else wants a remove method, etc. until you have duplicated a large chunk of the collection API in the container. When you do this for enough collections contained in fields, you have huge numbers of methods that do nothing other than repeat the methods of the collection fields, which can make a class's API largely unreadable. Limiting the repetition to a specific common case (like add, for cookies) seems a reasonable compromise.
- R On 2/1/08, Stephan Koops <[EMAIL PROTECTED]> wrote: > > a possibility is to add for every setter/getter pait returning a > Collection (or List, Set, e.g.) an add method. > Example: add for Collection request.getCookies() and > request.setCookies(Collection) add a method request.addCookie(Cookie). >
