It's simply a matter of style. Java developers tend to see the world as a strongly-typed one, and I prefer to specify a range of allowed inputs as a range rather than magic strings. The strings probably won't change, but it does expose an implementation detail of JRadius that I would rather keep hidden. By wrapping in an enum, we can easily respond to implementation changes without requiring CAS deployers making any configuration changes.