The question did popup again how to redirect to an url (external or internal doesn't matter)
We already had a RedirectPage that does a meta tag refresh (can be a delayed one)
But i also added a RedirectRequestTarget that can be used now.
Now the question is should we "hide" this target as we do with page ?
With page you just say: RequestCycle.setResponsePage(page)
so should i add RequestCycle.setResponseUrl()?
We could also add RequestCycle.redirectTo(url) but this resembles the redirectTo(Page) method
and that method isn't supposed to be called from the outside of the framework.
So what is easier?
1> use RedirectRequestTarget directly: RequestCycle.setRequestTarget(new RedirectRequestTarget(url));
2> have a RequestCycle.setResponseUrl() besides setResponsePage()
3> have a RequestCycle.redirectTo(String url)
i am thinking just learn how to use RequestTargets so 1 (thats how wicket really works)
But i can live with 2 but i am against 3.
johan
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
