I tend to put such things in XML files rather than properties files nowadays.
When the app starts up I have a plugin read the files and create configuration objects (using Digester), and put these objects into the servlet context (application scope) where my code can get at them easily. -----Original Message----- From: news [mailto:[EMAIL PROTECTED] Behalf Of j h Sent: Thursday, 8 July 2004 19:23 To: [EMAIL PROTECTED] Subject: application configuration If there are specific properties that need to be configured on deployment, where should these be put? you could put these in the application.properties file and read these in from an Action class every time they are needed: MessageResources mr = getResources(request); String config = mr.getMessage("configuration.detail"); This seems inefficient. Is there a way to read these into some global variables? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
