Hi, I and my colleagues decided to write a custom filter class to check authorization against a LDAP server Inside the Filter class we got some parameters or attributes such as netId and password from the HttpServletRequest object and we check that against the server. Our first page is a wicket page called LoginPage from this page we call another page adding in the HttpServletRequest two attributes (the netId and the password) WebRequest wRequest = (WebRequest)webpage.getRequest(); wRequest.getHttpServletRequest().setAttribute(...)...
In this way before the other wicket page is loaded the filter class is invoked, then the request object inside the filter class is completely empty without any attributes or parameters. Anyway if we get a HttpSession inside the LoginPage from the request object and we add in the session the attributes we are able to access them from filter class(the session in not empty). Anyone of you has already faced a problem such that. Thanks in advance Andrea -- View this message in context: http://www.nabble.com/HttpRequest-and-Filter-class-tp16945908p16945908.html Sent from the Wicket - Dev mailing list archive at Nabble.com.
