ChuckDeal wrote: > Hopefully, I don't have some unique scenario. We are going to migrate our > app over to the Wicket framework in pieces. To do so, app will technically > be based on Wicket and we will make calls back to the legacy code (JSPs).
Ah ha, thought so. I have already been down this road. It's a complex one. :) What you'd ideally like to be able to do is have a Wicket page which has a <div wicket:id="jsp"></div> in it, and render the JSP in there, yes? In fact, ideally, you'd probably like the page URLs to stay the same; "server.com/foo.jsp" rather than "server.com/HackPage/page/foo.jsp", am I right? Believe it or not, this is actually possible, although there are certain issues with it. I'm going to write this up on my blog so I can link to some example code and things, and I'll see if I can have that done for you before Monday. It's somewhat complex - I'm not sure it belongs on the wiki, because I'm not sure I want to have to support it. Like I say, try it without mounting your Legacy page and see if it works. If it does, it's definitely WICKET-40. We've recently been discussing making the URLs all generate in a single place, so we don't URL encode twice and have these kind of issues. I think we need definitely need to fix WICKET-40 before 1.3 goes out, so this should happen fairly soon. Al ------------------------------------------------------------------------- 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
