If the aim is only to prevent coding change in the event of value change than you can push the data to a properties file.
On Tue, Mar 23, 2010 at 4:30 PM, Mike Calmus <[email protected]> wrote: > I am in the process of converting several custom enumeration classes to the > Java 5 enum framework. This is going generally smoothly since our pattern > pretty much conformed to the generally-accepted style. There are a few of > these classes, though I'm struggling with. For some of our enumerated types > we retrieved values from the database to populate descriptions. This isn't a > problem for the named enums from this part since I can do the same lookup in > a constructor. Part of the point of doing these database lookups originally, > though was to have new values included in the enumeration without requiring > a coding change to explicitly name new values. These implicit (from the > database) enum values are the problematic pieces. Anyone have any ideas how > to deal with this? > > Thanks. > > -- > Mike Calmus > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
