Makes sense.. Is it possible to configure in the web.xml more than one wicket filter and conversely have more than one WebApplication class in my deployed web app? I was thinking for registration pages to point to a "reg" wicket app, and once a user is logged in, a different app for some pages.
The thing is, I am trying to intermix an existing badly written Struts/JSP pages, worse written JSP pages that point to each other and use ajax/rest calls to populate data.. and now trying to "fix" some of the bad pages by building wicket pages from them. Eventually the goal is to be pure wicket. But in the mean time, I gotta work around the existing pages. In many cases I am going to need to call the wicket pages from the existing pages. For example, if a user wants to register, I have to pop up a modal dialog box and hopefully use the new wicket registration pages I am working on in the modal dialog, then when it is done, close back to the existing pages. My thought was, the reg pages would be their own wicket app, and when I get to the logged in pages that I'll start to fix/add, make that a separate app so that the entry point into the wicket is another WebApplication and home page/class. So is it possible.. allowed, or bad to do? Thanks. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Having-problems-with-wicket-pages-not-showing-up-tp3784941p3785309.html Sent from the Forum for Wicket Core developers mailing list archive at Nabble.com.
