there are always package-wide property files support in wicket... -igor
On Wed, Jun 3, 2009 at 6:57 AM, Marcin Palka <[email protected]> wrote: > > Hi Jens, > > I would suggest to create a base page class that contains common elements > and then for each customer extend your base page class. This makes it > possible to keep common message keys in a base class property file(s). As > far as I know in case wicket is not able to find a message key in a property > file(s) with the same name as a class file it will look into its base class > property files as well. > > You may want to read this article (especially the "Finding the message" > section): > http://day-to-day-stuff.blogspot.com/2008/05/wicket-internationalization.html > > cheers > Marcin > -- > View this message in context: > http://www.nabble.com/Different-xml-property-filename-for-the-markup-and-java-tp23847329p23851943.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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]
