Column names (at least with DefaultDataTable) are supplied via an IModel<String> in the constructor of AbstractColumn, so you can supply whatever you want. Those values can come from a database, properties files, etc. You can use a ResourceModel to load the values from your page/component's properties file.
On Fri, Oct 15, 2010 at 6:06 PM, gouthamrv <goutha...@yahoo.com> wrote: > > I am looking for some design patterns or best practices for configuring web > page fields. > > My web page has a table, which is dynamically created by my API (Wicket). > > Currently all the column names are hard coded in the java but I want to make > it externalizable that way I can add/remove/modify fields without modifying > java code. > > Also I want to define each field type, valid value ranges etc.. in this > external file. > > Are there any recommended approaches for this requirement? > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/How-to-externalize-web-page-elements-to-make-it-configurable-tp2997775p2997775.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
