I would have expected <table> <tr><td>Foo1</td><td>panel.foo1 from page.properties</td></tr> <tr><td>Foo2</td><td>panel.foo2 from page.properties</td></tr> <tr><td>Foo3</td><td>foo3 from page.properties</td></tr> </table>
a) panel.fooX is more specific than fooX and should take precendence b) assume you purchase (no source code) a ready made set of wicket components with pre-configured properties which you can not change. But since it is a component you will add it to a page, panel whatever. Hence adding a property to page should overwrite what is pre-configured by the vendor. Which however is a little bit dangerous since if you add another component with the same id to the page (no path), they may end up using the same property. Juergen
