Well, if the list is large, storing it in the database might be the best option (it is also a good idea because you will be able to alter it without messing with the application files and possible triggering an unwanted application restart)
But, if it is something more like
a configuration settingthen you can use the components.xml file to configure the properties of a bean, I use that for custom configuration settings.
Another option, if you are using the Spring/Seam integration is to use applicationContext.xml
We use a foo.properties file which is placed in %JBOSS_HOME%\server\xxx\conf which can be changed for different envmts (dev, QA, UAT, etc.)
and we also use db tables (this is the best option, the changes don't require a server restart)
Thanks. Assuming that the file is called custom.properties, and it has a property called the following
Do you reference and read it this way?
Do you need to instantiate anything or can you simply reference it using expression language? Thanks.