These are workaround ideas, so please excuse the design choices.
// anonymous inner approach
enum E {
A() {
final String thing = "DEV_PR"
// add read-only properties or getter methods for Type1.M2, Type1.DEVELOPER,
"Progr", "Programmer", [cat.WHITE_COLLAR, cat.PROPELLERHEAD]
},
B() {
Another thought would be to convert this code-based design to a data-driven
approach. Would an in memory database or a JSON/XML resource file be a better
place to represent and store the 1200+ entities?
-Original Message-
From: Milles, Eric (TR Technology)
Sent: Saturday, February 25,
