A Set is too restrictive i think, there are valid reasons for preserving duplicate configuration entries. I would use a Collection or better, a List when the element order matters.

Emmanuel


Eric Pugh wrote:

Hi all,

I am looking at a chunk of code like this:
 Vector packages = Turbine.getConfiguration()
                    .getVector(TurbineConstants.MODULE_PACKAGES);

                ObjectUtils.addOnce(packages,
                        GenericLoader.getBasePackage());

from Layout Loader...

And it seems to me that commons-configuration getVector should be deprecated
in favor of getSet().  I can't think why you would want duplicate values, so
getSet() makes more sense then getList().

Then, funky call's like the ObjectUtils.addOnce() wouldn't be needed...

Opinons?  And do we have to deprecate getVector() since we haven't released
from sandbox yet?

Eric Pugh


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Attachment: smime.p7s
Description: S/MIME Cryptographic Signature



Reply via email to