David, Given your requirements, I'd recomment putting them in a properties file along side your custom WebApplication class for your particular application and then inside of the WebApp's init method, reading in the properties file and storing the information in the WebApplication.get/setMetaData methods to store that free-formed information: http://wicket.apache.org/docs/1.4/org/apache/wicket/Application.html#getMetaData(org.apache.wicket.MetaDataKey)
<http://wicket.apache.org/docs/1.4/org/apache/wicket/Application.html#getMetaData(org.apache.wicket.MetaDataKey)>You could be fancy and spin off a thread that checks every 10 mins for changes to the files and re-sets the metadata info if you want to be able to change that data while the app is running without a restart. Either way, it's just a plain properties file. Best, Riyad On Sun, Mar 7, 2010 at 1:15 PM, David Chang <david_q_zh...@yahoo.com> wrote: > Hi, I am new in Wicket. > > I did Spring web applications before and I usually put an app's > configuration parameters in the application context file. > > I would like to know the best practice in Wichet for setting parameters > such as SMTP server, LDAP server, etc. Where should I put them? I dont feel > WebApplication is a good place. Put them in an old java properties file? I > want these parameters can be changed without touching source code. > > Thanks! > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
