> The 'best' (IMHO, YMMV) way to handle a situation like this
> is to think
> not in terms of data elements, but rather in terms of the container.
> What you're after is a container with the properties of a Vector, but
> which quietly rejects attempts to add items already in the Vector (for
> the appropriate sense of equality). Make the globally-referenced
> container be an instance of such a type, and you get the
> right behavior
> everywhere, with no extraneous code changes.
This does look cleaner to me. However, the getVector() code
goes deep into several basic classes, including a couple under
org.apache.java. I don't want to touch this code; maybe if
you find a good way of achieving this, you could do it?
--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
