tags:

views:

185

answers:

3

hello guys i'm not sure if the title is descriptive enough.what i mean is creating an enum like so

public enum Test{
  ONE, TWO ,THREE
}

this looks like hard coded.if for some reason i need to add the FOUR some certain business rules evolution reasons.should i code it and deploy it again? isn't a way to let it pick the elements from a file , spring config for example or property file? THanks for reading.

+1  A: 

You may store in a database table.

Daniel Moura
thans for the reply.i saw one example using hibernate.Not bad at all but not good for my project.
black sensei
+2  A: 

I asked a similar question here. The content may be of interest.

The concensus seemed to be that Java's enum type is static by design. If you need something that can be altered at runtime, you should ideally use a different data structure.

The less preferred ideas were along the lines of extending Enum, etc.

Brabster
+5  A: 

If the enum value doesn't explicitly exist in code, how could you ever use it? Test.Four would not compile. Any code which could somehow reference Test.Four would be invalid and would crash, until the point in time when the file is read and the new values are added.

You can, of course, use arrays or collections of values and manipulate those at runtime - load them from a file or from the database or whatever - but not enums.

Rex M
thanks for the explanation
black sensei