Hi Roger,
> That would work in this case, but my interceptor would be specific to the > wizard. If I then introduced a second wizard, then I'd need another > interceptor to handle that one. I was hoping for something a little more > generic. Won't You also add more bussiness logic if You add another wizzard? It's hard for me to imagine such a generic tool that will do it without a lot of configuration or writing this special logic into some class. But if You will find such a solution please write back about it. > So how would you deal with a client opening two tabs and editing an order > for two different customers in > each? I could put key information such as customerId & orderId into a form > as a hidden field, but I "like" to retain that in the session to facilitate > detecting malicious update attempts - I can check that the > customerId/OrderId coming back are the ids that I originally sent - for > example. Every form needs to have all necessary ids as hidden fields. That way, posting a form will always update appropriate object with appropriate data. And it's completly unimportant from which tab it will be submited. As for me, user can open 15 tabs and do 15 different things in them simultaneously. Imagine a list of objects with edit links, user opens these edit links in new tabs, and wants to edit and save one by one - why would You dissallow it? In the end HTTP is stateless. Best greetings, Paweł Wielgus. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
