Well, my workaround worked as I'd hoped. And it was dumb-ass simple injecting a custom filter.
All relative "src" attributes are prepended by a hardcoded public URL. All relative "href" attributes are prepended by a hardcoded contextRoot. All page links are left "as is" because they are working fine. > Even if it is just your setup it would be good to find out what it is, > so we could try to detect such issues in an earlier stage with Wicket. > Ideally, Wicket should work for any setup. All I can suggest is that the way the PrependContextPathHandler works (i.e. getApplicationSettings().getContextPath()) must not be the same as the way the whatever-it-is class that takes care of mounting pages. They are clearly not getting their contextRoot values from the same place, else they would both work the same way, I think. In PrependContextPathHandler, it only gets the correct value if I explicitly set it. For mountable pages, it manages to get the correct value whether I explicitly set it or not. HTH ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
