To answer my own question, a quick peak at the code shows that Wicket loads properties using java.util.Properties, which simply parses a stream for key-value pairs. It does not do any property expansion/substitution the way that developers might expect based on their experience with tools like ANT.
There are alternatives to Properties
, like Apache Commons Configuration, that perform expansion but Properties
does not. Therefore, neither does Wicket - it simply loads the properties as they are written. The only substitution Wicket does is for model properties when a page is rendered, not for properties in the "properties file" sense of the word.