Final context-path-problem solution

[mcbain <ma...@jens-zastrow.de>]

Hi

My wicket-app runs with the standalone-jetty without errors.
After deploy it to a tomcat-container the "webapp-context" problem arises,
since the 
webapp-name is included in the url e.g. http://abc.de/webapp/. 
Wicket 1.4 generates relative resource-uri '../css/' in that case, which are
not correct.
What is the official solution to solve this issue?
I read that Wicket 1.3 was reconfigurable for such case!?
Or have one to use the "apache-proxy solution" (wicket-wicki) to hide the
/webapp/?

Thanks


-- 
View this message in context: http://www.nabble.com/Final-context-path-problem-solution-tp20261844p20261844.html
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: Final context-path-problem solution

[mcbain <ma...@jens-zastrow.de>]

Solution 1
---------
Use wicket behind apache-http works as desribed in the wiki. 
-- 
View this message in context: http://www.nabble.com/Final-context-path-problem-solution-tp20261844p20263287.html
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org