This week's book giveaways are in the iOS and Features new in Java 8 forums. We're giving away four copies each of Barcodes with iOS: Bringing together the digital and physical worlds and Core Java for the Impatient and have the authors on-line! See this thread and this one for details.
Originally posted by Anurag Mishra: there is only one page which needs to handle the roleList. And different Users will be having different Role lists.
The most common approach, that I've seen so far, is to put the Array as an accessible property of the Form Bean. The population of this property would be done by the Action class. Since form bean instance would at most be in session scope, these lists would remain different per session/user.
I have one more question is there some other Place apart from ActionClass from where I can get the reference of my EJB and call the method??
Purists say that putting any logic which is even remotely related to business requirements, should not be part of the Action code. However, I found it too cumbersome to create one more layer/facade, since my application is really not massive. Most Actions in my code are implementing Sequence diagrams related to the UI logic.
Thanks and Regards, Kinjal Sonpal
Joined: Jun 16, 2003
Thanks for your reply Can you Explain what you mean by Most Actions in my code are implementing Sequence diagrams related to the UI logic.
Please just explain so I can implement this in an efficient way.
thanks in advance Anurag
Joined: Jun 06, 2003
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 ]