Will Jackson wrote:
What is the proper way to declare a default <wicket:child /> and
ensure that the page containing the <wicket:child /> is not directly
accessible on its own?
I know I can just call the extending page (i.e. Page1 extends
BasePage, calling Page1.html), but how do I ensure that BasePage.html
is not directly accessible? When I call the page in the browser it
just shows a blank region where the page extension will appear. What
I really want is possibly a 404 response.
Make BasePage an abstract class.
Regards,
Al
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
