Thanks. Just like everything else in wicket it's really simple.
We could consider adding it as a default implementation. But then
someone would have to make an example too...
I can volunteer for that. I plan to use something like that so I could add
an example with J2EE declarative security.
Both? :-) You could try doing a Wiki page seeing how much ends up
being code, vs code text?
If code then possibly as a part of wicket-examples (although the I
don't know if server-side requirements might rule that out) or a
standalone one as a project below wicket-stuff? For that, personally
WIKI page would be very welcome as Gwyn said. A basic example might go
in wicket-auth-roles-examples and this default implementation would go
in wicket-auth-roles. It would be great to have a patch for that. If
you have, please attach to an issue here
Hi,
I have seen some examples of how to write a wicket login page, but these
examples do not use J2EE declarative security.
Is it possible to use J2EE declarative security with wicket? Does the
wicket-auth framework support this?
Cheers
Erik
Should be easy to do: implement a custom IRoleCheckingStrategy and use
((WebRequestCycle)RequestCycle()).getHttpServletRequest.isUserInRole.
Eelco
On 8/24/06, Erik Brakkee [EMAIL PROTECTED] wrote:
Hi,
I have seen some examples of how to write a wicket login page, but these
examples do not
Like this:
public class JEERolesStrategy implements IRoleCheckingStrategy {
public boolean hasAnyRole(Roles roles) {
HttpServletRequest request =
WebRequestCycle.get().getWebRequest().getHttpServletRequest();
for (String role : roles) {
couldnt help yourself could you? :)-IgorOn 8/24/06, Eelco Hillenius [EMAIL PROTECTED]
wrote:Like this:public class JEERolesStrategy implements IRoleCheckingStrategy {
public boolean hasAnyRole(Roles roles) {HttpServletRequest request
We could consider adding it as a default implementation. But then
someone would have to make an example too...
Eelco
On 8/24/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
couldnt help yourself could you? :)
-Igor
On 8/24/06, Eelco Hillenius [EMAIL PROTECTED] wrote:
Like this:
public