And the servlet container already do tell us what it is through the request.
So why would you again have it configurable?
you can override it if you want just make your own Request class or WebRequest/ServletWebRequest sub class)
ContextPath is configurable because it can differ from what the request says and what it really is
because of virtual hosting.
johan
On 5/23/06, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
On Sunday 21 May 2006 15:07, Johan Compagner wrote:
> trunk is now 2.0 and is under heavy commit/changes so it can be that some
> test will fail.
> I thought they all run, but will check again.
I have essentially solved the problem we discussed on ICQ yesterday. It is a
bit hackish and not something elegant.
What would be elegant is being allowed to tell Wicket what the servlet-path
is, via one setting in application object... Then I could get rid of an ugly
dynamic Proxy on the http request...
Guess that is too late for v1.2. ;o(
Anyway... Thanks again Johan, for your time yesterday.
Cheers
Niclas
-------------------------------------------------------
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
