Enums - a good way to hold configuration data

Question

Im struggling with a good way to encapsulate configuration data.
In a configuration class I have this:
public enum TagResultsSize {
         ALL (false),
         SUBSET (true);         
         TagResultsSize(Boolean limited) {
            this.limited = limited;
         private Boolean limited;         
          public Boolean isLimited() {return limited;}
          private Integer maxTags = 10; // default max values - set by configuration if declared
          public Integer getMaxTags() {
               return maxTags;
          public void setMaxTags(Integer maxTags) {
               this.maxTags = maxTags;
    }When the application starts up I read some configuration XML and set the value of maxTags.
Then anywhere in my code I can request ALL, or a SUBSET of tags to get from the db.
I do a check if the enum value isLimited and if so get the maxTags value to set in my DAO.
The idea behind the enum I thought is that I can couple the CONSTANTS with the changing parameters from the configuration.
Can anyone suggest a better way of managing configuration data such as this?
Thanks
Jon
[Spring Web Development|http://www.springwebdevelopment.com]
Edited by: JonJackson on Apr 23, 2009 2:16 PM
Edited by: JonJackson on Apr 23, 2009 2:16 PM
Edited by: JonJackson on Apr 23, 2009 2:18 PM

Answer 1

Not really sure what it is you are trying to do. Why wouldn't these equivalent method signatures work just as well:
public Collection<Foo> getConfiguration(final int maxTags);
public Collection<Foo> getConfiguration();- Saish