We have a separate filter set up to catch parameter-less domain name requests ( /* ) like: www.myurl.com <http://www.myurl.com/> and forward them to a bookmarkable home page like: www.myurl.com/content/home/o/123 The extra o/123 is an organization discriminator name/value pair and is read in by the home page as a parameter. The use of a forward means that the address in the user's browser remains as www.myurl.com <http://www.myurl.com/> but the actual page rendered is www.myurl.com/content/home/o/123 The page mount looks like: pageParametersEncoder = new UrlPathPageParametersEncoder(); mount(new MountedMapper("/content/home", HomePage.class, pageParametersEncoder)); The code used for the forward inside our separate redirector filter is: RequestDispatcher rd = req.getRequestDispatcher("/content/home/o/123"); rd.forward(req, res); This filter then does not chain to the next filter so that the servlet engine can re-request with the forwarded URL. In 1.4 the wicket filter then services this forward request and renders the page without a problem. In 1.5 this no longer works and I've tried many different ideas to get it working but it just doesn't seem to want to work properly. Somehow wicket attempts to render a page with a url of: www.myurl.com/123 In other words the /content/home/o/ part has been stripped from the "forward to" URL. Debugging shows that the wicket request does indeed have the full uri: /content/home/o/123 <http://www.myurl.com/content/home/o/123> Any ideas what might be causing this? Yours sincerely, Chris Colman Pagebloom Team Leader, Step Ahead Software
pagebloom - your business & your website growing together Sydney: (+61 2) 9656 1278 Canberra: (+61 2) 6100 2120 Email: [email protected] <mailto://[email protected]> Website: http://www.pagebloom.com <blocked::http://www.pagebloom.com/> http://develop.stepaheadsoftware.com <blocked::http://develop.stepaheadsoftware.com/>
