> > I would like to submit a patch for this...
> The component should be in there though. It currently doesn't have any
> issues assigned, so it doesn't show up on the front page, but if you
> create a new issue, you should be able to select it.
Ok, you're right Eelco. I'm honoured to be the fi
> I would like to submit a patch for this, but I can't see where I need to
> do this...
>
> I can see that the issue tracker is now Jira set up on the Apache
> infrastructure, but there is currently no component for
> "wicket-auth-roles".
The component should be in there though. It currently doesn
I would like to submit a patch for this, but I can't see where I need to
do this...
I can see that the issue tracker is now Jira set up on the Apache
infrastructure, but there is currently no component for
"wicket-auth-roles".
Assuming that this is where I need to send in my patch, could somebod
> Is there an elegant way to do the opposite of what the AuthorizeAction
> annotation was intended for?
>
> I have an "unregister" function that any user _except_ the admin user
> should be able to use. If the admin unregisters, I'm f*.
>
> Essentially, I'd really like to be able to do somethin
Is there an elegant way to do the opposite of what the AuthorizeAction
annotation was intended for?
I have an "unregister" function that any user _except_ the admin user
should be able to use. If the admin unregisters, I'm f*.
Essentially, I'd really like to be able to do something like this
