with a statelesslink you cant rely on state on the server so final fields and all of that dont work. The link should be able to do it job on a page that is just created... thats the most important thing to remember.. So no state from a model (except if the model is already usable on page creation)
On Wed, May 7, 2008 at 2:42 AM, Ritz123 <[EMAIL PROTECTED]> wrote: > > Hi, > > I have a page containing bunch of products and addToCart link next to each > product. On clicking the add to cart link, would like to add product to > cart. I had Link and onClick() to do this - but recently encountered page > expired message which is expected since the page becomes stateful due to > the > Link. > > Obviously this page is supposed to be stateless and hence I changed Link > to > StatelessLink using final product id inside the onclick. Now on > application > reload(due to hotdeploy) to simulate session expiry, dont get session > expired message but link behaves weird in the sense, it seems to be > reloading the contained page instead of going to the setResponsePage. > > Seems like I may be missing something. Is this the right approach in terms > of making the page stateless? > -- > View this message in context: > http://www.nabble.com/Stateless-link-usage-tp17093682p17093682.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
