Hi Matt, Thanks for the prompt reply as usual!
mraible wrote: > > My thought process was that if you're editing an existing record, you > want to visually see the change after you've made it. When adding a > new record, it's likely you don't want to see the change. That was my > thinking when I did it this way. > OK, I understand that thinking. In this situation, my users always want to go back to the list screen after clicking the "save" button, so it seems like I can achieve this simply by having any successful save return "SUCCESS". I note that failed validation causes an INPUT return so I need to use that to return to the edit screen. I have to say, I'd originally expected failed validation to return ERROR, but I expect there's some logic there I'd not thought of. Cheers, Rob Hills Waikiki, Western Australia -- View this message in context: http://www.nabble.com/AppFuse-2-%2B-Struts-2---Why-does-save-action-return-INPUT-for-an-existing-record--tp19395366s2369p19395610.html Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
