Do you have a summary of your view? and preferably a very simple flow chart or example? There have been a trillion posts lately and haven't had time to sift through them all.

All I can say is the concept of the ActionForm was initially proposed so that the user can be given back exactly what he entered when validation failed. I certainly don't want more Action forms. Because I have to develop code in a situation where I have tons of nested properties, I could actually code without any ActionForms (since typically my ActionForm would only hold one bean which holds a collection of other beans each with their own collections, etc etc. It's just the nature of the beast of the objects I have to work with coming from the backend and for the types of data entry that needs to be done).

Convincing me that 'more' ActionForms are a good thing is going to be a difficult task, but restate or post your summary propostion and I'll 'attempt' to look at it without any preconceived notions that you might be crazy:)


Dakota Jack wrote the following on 3/17/2005 2:04 PM:
I have put forward a very basis description of what I take to be a
compelling case for multiple ActionForms for Actions.  I encourage any
of you to hammer what I say there, add to the facts, straighten out
the logic, etc., because for me this is an very important point.  I am
surprised if it is not an important point for all of us.  Surprise me,
if it is not.

I am ready to see that I am missing something, because Ted thinks
otherwise and he usually is the epitome of good common sense in
coding.  I don't see it here and am open to being taught something
new.

Jack



--
Rick

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to