Yes, it is a known issue, and we had the luxury to solve it via Apacher Httpd proxying instead of tackling it head on. Also, at the time Pax Web didn't exist, and the available ungoverned.org HttpService had many "mounting" and path resolution problems. It might be that Pax Web's support is better and this should be resolved.
First, I suggest you create a Jira issue about it, so it won't be forgotten... -- Niclas On Sep 29, 2009 10:34 PM, "Andrew Williams" <a...@handyande.co.uk> wrote: Hi, I am investigating the use of pax wicket in my current project and so have checked out the department store samples. Whilst the app seems very powerful I have a requirement that messes it up - the need to mount at the root (/). If I change the sample app to do this the css fails to load - the URL returns a 404. Is this a known issue due to the usage of servlets instead of filters? Let me know if I can provide any more information, Andrew _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
