Re: [Wicket-user] Best practice: Global configuration values?

2005-12-05 Thread Eelco Hillenius
The logical place here would be your Application/ WebApplication object. You could combine this with init parameters in web-xml and reading them in the Application.init method. Or, in case you want to use Spring, use Spring config to configure your Application properties. Eelco On 12/4/05,

Re: [Wicket-user] Best practice: Global configuration values?

2005-12-05 Thread Johannes Fahrenkrug
Thank you for your reply. Eelco Hillenius wrote: The logical place here would be your Application/ WebApplication object. I looked into that, but are these values accessible from every page? - Johannes. On 12/4/05, Johannes Fahrenkrug [EMAIL PROTECTED] wrote: Hi, I have a short

Re: [Wicket-user] Best practice: Global configuration values?

2005-12-05 Thread Eelco Hillenius
Yep. You can get the application from several places, like Component.getApplication (and note that Pages are Components too) or as a falltrhough, when in a request, you can always call Application.get() (slightly less efficient though, as that is done by threadlocal map lookup). And you have to

Re: [Wicket-user] Best practice: Global configuration values?

2005-12-05 Thread Johannes Fahrenkrug
Eelco Hillenius wrote: Yep. You can get the application from several places, like Component.getApplication (and note that Pages are Components too) or as a falltrhough, when in a request, you can always call Application.get() (slightly less efficient though, as that is done by threadlocal map