This content has been marked as final. Show 2 replies
greybird wrote:Well, all configuration parameters could be passed as Strings and internally parsed into appropriate long values. Meaning, the current "long" configuration methods would be marked as deprecated (and visibility changed to protected in an upcoming major release).
You have a point, but since the values are type Java long, it isn't something either easy to change, or high priority.
Then all configuration parameters could be corralled into an "enum" and a single additional method would be introduced, namely
setConfigValue(PARAMETER parameter, String value) throws InvalidArgumentException
greybird wrote:Well, yes, sigh :-)))