Al Maw wrote: > > It looks like you're trying to link to an external JSP, but that for > some reason you're doing this via with a setResponsePage(), which is > most definitely only for Wicket-based pages. >
Close, I am passing the legacy url to the LegacyWrapperPage (mounted as Legacy) in order to load the legacy *inside* the context of a wicket page. I do this by putting an iframe in the LegacyWrapperPage and loading the legacyUrl parameter into that IFrame. I encode the legacyUrl (to avoid any conflicts with /, ?, or &) in the code the generates the Link to the LegacyWrapperPage. Al Maw wrote: > > If you look at your URL, it has things like %252F in it. This is a > doubly-URL-encoded version of "?". > > It seems likely that this might actually be a URL escaping bug caused by > you embedding your JSP paths in a Wicket page parameter on a mounted > page URL, which is this one: > http://issues.apache.org/jira/browse/WICKET-40 > I'm not quite sure how it is getting double encoded, I'll see if I am doing it. Perhaps you are right, I know I was experiencng problems with my legacyUrl getting decoded to soon(?). It was when I was using the AjaxRequestTarget.appendJavascript(). The String the I sent to the page (and verified via the ajax debug window) was correct, but when the javascript was evaluated, it got decoded too soon (maybe?). Al Maw wrote: > > Are you wrapping your old JSP pages inside a Wicket page using a > RequestDispatcher? I might be able to give you some cunning advice on > how to make all this work. > Right now, I'll take any advice. I'm shooting from the hip and I'm not sure if I'm even hitting the target! What I have appears to be working, sort of. Al Maw wrote: > > If you don't need to wrap a Wicket page around your JSPs, then you > should probably be creating your links to them directly, rather than > creating a Legacy.java Wicket page that takes JSP paths as a parameter. > > Can you give me a bit more detail? Feel free to respond off-list, or > open a JIRA issue and attach some code. > I do need access to the Wicket framework because I am using Databinder/hibernate and it just makes things easier/better to be able to utilize some of that in the legacy backend. I also created a special filter that fires after the WicketFilter that is designed to handle legacy pages as well, but I need to be able to navigate among the pages as semmlessly as possible, and heres the clincher, I need it to require as few changes to the legacy code as humanly possible. Hopefully, I've given you a rough idea of what I am attempting to do. I'd be glad to share whatever I can, I'm just not sure where to start. Chuck -- View this message in context: http://www.nabble.com/relative-urls--tf3195723.html#a8890498 Sent from the Wicket - User mailing list archive at Nabble.com. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
