Originally posted by Anurag Mishra:
Can you Explain what you mean by
Most Actions in my code are implementing Sequence diagrams related to the UI logic.
Anurag, I'm sorry for ambigous statement like this.
A typical execute(or equivalent) method in an Action class of mine would have something like this :
Fetch validated user input from FormBean, construct VOs, push VOs thru' XyzManager for business processing(XyzManager will push data to the back-end by using XyzDataManager), fetch x or updated data from XyzManager, put them into the FormBean, forward to relevent mapping.
While designing the application, our (so-called) architect had develeloped several use-cases and corresponding sequence diagrams to explain the flow of data and control. At that time the decision to use
struts was not in sight. These are the sequence diagrams that my Action classes are implementing.
I hope I'm being clearer here. I'm not having a very detailed understanding of Designing and architecting lingo and principles.
Let me know about your views.
Thanks and regards,
Kinjal Sonpal
[ June 04, 2004: Message edited by: Kinjal Sonpal ]