But still... Everything I read says that wicket searches for property files on class hierarchy and nesting. And that a good thing of cource. But... Lets say that I would like to have one big xml property file for every functionality package (that our customers might want to buy). Most of the pages in that package is built up of different panels but they share a lot of properties. I cant use the MyApplication.xml because its in the core package. But I got two base webpages in the core webapplication package(that contains the Application class). One webpage for basic layout where I'm using wicket:child. And one webpage that I using in modalwindows. Im willing to extend them for the func. package but I dont want to duplicate all the properties in these to pages propertyfiles. In my case I cant see how the wicket class hierarchy and nesting could help me.
But I dont understand what you meen with package-wide property files. I know two ways of hooking up on property files in wicket. 1. Nesting and hierarchy 2. getResourceSettings().addStringResourceLoader in the Application.init I cant use number 2 because Its in the core package Jens there are always package-wide property files support in wicket... -igor -- View this message in context: http://www.nabble.com/Different-xml-property-filename-for-the-markup-and-java-tp23847329p23865653.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]
