thats 1.5 btw, in 1.4 you can do /context/filter/?wicket:bookmarkablePage=:<class>
-igor On Thu, Sep 1, 2011 at 5:56 PM, Igor Vaynberg <[email protected]> wrote: > if your pages are bookmarkable, but you dont mount them you can access > them via a url like this > > /context/filter/wicket/bookmarkable/<classname> > > -igor > > On Thu, Sep 1, 2011 at 4:46 PM, jlazeraski > <[email protected]> wrote: >> Thank you for the reply. Indeed there is info on mounting, but being new I >> would not have known that other than the main page, every page must be >> mounted to access it. In examples, there is no info on "mount the URL so you >> can test this page". So unlike when buliding with jsf, jsp, or even normal >> html where I can simply access the page, in Wicket, without mounting, the >> only page I can access is the home page returned by the Application class? >> So I take it the home page must provide links that when clicked and handled >> in the Wicket class that represents the page, it then forwards to other >> pages within wicket? In other words, there is typically only one entry into >> a wicket app, unless you make a bookmarkable page (and/or mount it)?. That >> info isn't made clear up front that you don't navigate wicket pages like you >> do pretty much every other framework. >> >> So in my case, my site has several static pages that the user clicks around >> from the home page.. basically reading info on why they should use our >> service.. etc.. and then a login button and a register button. Those lead >> into dynamic form pages. So if I want to build the static pages yet utilize >> a shared header/footer bit, is it typical to do these in wicket still to >> share a common header/footer, much like jsp includes? If so, then how do I >> "test" these pages.. do I have to always refresh the main home page then >> navigate to the page I am working on? For that matter, I would assume static >> pages like this that don't require a user to be logged in (or any session >> state), but do want to share a common header/footer, should be mounted >> and/or bookmarkable so that they can be accessed directly? >> >> Thanks. >> >> >> -- >> View this message in context: >> http://apache-wicket.1842946.n4.nabble.com/Having-problems-with-wicket-pages-not-showing-up-tp3784941p3784999.html >> Sent from the Forum for Wicket Core developers mailing list archive at >> Nabble.com. >> >
