Re: shopping cart and back button
I have a user case like this: 1. User opens products page. 2. User chooses a product. 3. User clicks add product to shopping cart. 4. User is redirected to shopping cart list. 5. User clicks _back button in the browser_. 6. Added product in step 3 disappear from the shopping cart :( So is the problem that the item is removed from the list again, or that you display an old page? How can I fix it? If the item is actually removed from the list: make sure the addition isn't recorded as a state change (I think it only is when you call setModelObject). Turning versioning off for the page that does the adding (override isVersioned and let it return false) is another way to avoid this, and in fact 'turn off' the back button for that page altogether (because no different versions are generated te URL stays stable). Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Paging Navigator
i think this is the only place we put markup into code. and it is because this is a global setting, so what markup template would it go to? and because the html fragment itself is tiny - usually just a single tag. -igor On 8/11/07, Mathias P.W Nilsson [EMAIL PROTECTED] wrote: Thank you for that fast response. Work fine. I'm just wondering. Isn't it against good web programming rules to add HTML code in the java code? Isn't that what all new template based frameworks ( Struts 2, Tapestry, etc ) is trying to avoid? // Mathias -- View this message in context: http://www.nabble.com/Paging-Navigator-tf4254110.html#a12108063 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Paging Navigator
you can always extend it to do what you want. those components are pretty old, been untouched since probably before 1.0because they seem to work for the vast majority of users. if you want to improve it you can always attach a patch to jira. -igor On 8/11/07, Mathias P.W Nilsson [EMAIL PROTECTED] wrote: Yes! Your right. Had been great if it had wicket:id=emptyLink so that you could mark up the code. Maybe like a ul, li list and display:block in css to make it both vertical and or horizontal. -- View this message in context: http://www.nabble.com/Paging-Navigator-tf4254110.html#a12110934 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
