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
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.
