I have successfully used Al Maw's technique for embedding legacy jsp content into a wicket page. When loading the page into the browser via address bar or another link, it seems to work great. However, if I attempt to load the page in a popup window the relative paths get broken. I can't seem to figure out why there would be a difference; when tracing through ServletWebRequest.getRelativePathPrefixToContextRoot() they seem to produce the same value, however in the popup's case, the images aren't displayed.
I don't understand why using window.open to open a page vs using the address bar of the main browser should be having this effect. Would anyone care to take a shot at solving my issue or even hypothesizing what the problem is? Wicket 1.3.0-SNAPSHOT (revision 576365) IE 6 Tomcat 5.5.17 Thanks Chuck -- View this message in context: http://www.nabble.com/JSP-embedded-in-Wicket-page%2C-loaded-in-a-popup-window-tf4496759.html#a12823571 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
