Well at least I understand how the thing is supposed to work now. Before I posted here I searched every where I could think of to understand this behavior and the struts documentation certainly wasn't complete in this regard.
So thanks for working through the problem guys.
What this does do though is seem enforce a one to one relationship between forms and Action classes. I know that's what your supposed to do but it might have been convienient if you had two seperate forms with similar data (scope) both going to the same action class to be handled there.
(a little thinking out loud follows here...)
I usually have a service layer that doesn't know anything at all about struts or http that looks after the data model. I like abstracting the layer away from the action class. The idea that the action class should mediate between the forms and data model doesn't really seem to sit right in my mind.
I thought that potentially with an Action Class that could handle more than one method (by mapping submit buttons to methods) might make my life easier because your action class could look after a grouping of similar forms (but each form would have a seperate default submit action if no button had been activated, so you would never be able to tell which form actually submitted with the default submit action).
So maybe that's a bad idea.
Anyway thanks again for guys.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
