Please do, yesterday i checked in some changes that should redirect
you to the login page if you place secure components on a non secure
page.
All the documentation and examples are still work in progress but you
could check out the junit tests and the documentation here
http://wicketstuff.org/con
The override of onUnauthorizedPage didn't work because the framework was
throwing the UnauthorizedInstantiationException because the page itself was
not secure, but the component was. I was able to handle this by overriding
the WebRequestCycle to handle exceptions explicitly as indicated in the
pr
Hi,
On 6/3/07, Maurice Marrink <[EMAIL PROTECTED]> wrote:
> Not sure if it is the preferred way of doing things (since this is
> Eelco's framework)
That part is actually Jonathan's
> but you could override the init() method and set up
> a different authorizationstrategy and or instantiationliste
Not sure if it is the preferred way of doing things (since this is
Eelco's framework) but you could override the init() method and set up
a different authorizationstrategy and or instantiationlistener, all
you have to do for that is skip the call to super and do something
similar yourself.
Or you
I am using the AuthenticatedWebApplication package. I would like to do
component level authorization. The framework generates an exception for this
that I can't see how I can override. Basic behavior is to be redirected back
to Home Page. My reason for doing this at the component level is to make
