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, Johannes Fahrenkrug <[EMAIL PROTECTED]> wrote: > Hi, > > I have a short question: What is the Wicket way of making configuration > values accessible throughout the application? > This it the scenario: My application can run either in development or in > production mode. In development mode it should connect to a different > RMI server than in production mode. Multiple pages have to connect to > the RMI server. Is there a best practice of making certain values > accessible from every Page? (making my own page that extends Page and > holds such values comes to mind, but is there a different way?) > > - Johannes. > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Wicket-user mailing list > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
