-Igor
On 4/11/06, Gustavo Hexsel <[EMAIL PROTECTED]
> wrote:
Juergen gave me some pointers and I decided to try migrating to 1.2. I have to say things are quite a bit more complicated now... how do I get access to the request from an AuthorizationStrategy? I need to check if the request's IP is within a pre-configured range. Before, I was doing this on checkAccess():
final ServletWebRequest servletWebRequest = (ServletWebRequest) getRequest();
final HttpServletRequest request = servletWebRequest.getHttpServletRequest();
final String clientIP = request.getRemoteAddr();
boolean isOffSiteIP = ConfigurationService.getInstance().isOffSiteIP(clientIP);
boolean isOffSiteAllowed = ConfigurationService.getInstance().load().isOffSiteAccessEnabled().booleanValue();
if(isOffSiteIP && !isOffSiteAllowed){
... redirect to appropriate warning page
}
[]s Gus
-----Original Message-----
From: Gustavo Hexsel
Sent: April 10, 2006 6:10 PM
To: '[email protected]'
Subject: WicketTester and checkAccess redirections
Hi,
I'm using Wicket 1.1.1 and trying to get my first WicketTester to work with the current app. I can't seem to get the redirectToInterceptPage(Page) method to actually redirect to the page. It works fine from Tomcat and Jetty, but the WicketTester seems to ignore the call (though I stepped into it and saw it was actually called).
Is this the expected behaviour? If so, how do you test the interceptions?
[]s Gus
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmdlnk&kid0944&bid$1720&dat1642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
