go through the struts documentation carefully..It will help u clarify lot of doubts..:-)) It specifically says Action classes are multithreaded..Means same action instance is used for all the requests..so thats why u have to be careful not to have any attributes in the action...So long as they are not really global.
-----Original Message----- From: kelly [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 06, 2003 12:32 PM To: struts-user Cc: kelly Subject: Re: What should and should not be in an Action class. Sweet. That's just what I was planning to do. Thanks for the verification. I have only one question about it though. When the Action class is called by more than one user, is it instansiated more than once by struts or will struts use the same instance? Cheers, and Thanks again, Simon ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, February 06, 2003 12:27 PM Subject: RE: What should and should not be in an Action class. > U will have some thing like following .. > > The action classes are handlers...So when u need to get some data to the > screen,U will call the action class and the action class will then call a > Busines Layer class to perform the database access logic and return the > result.And action will then put the result in required scope(mostly in request > scope ) and forward to jsp.The jsp will then use this data,usually a java bean > ,to render result. > (Lets take an example...To get EmkployeeDetails,u will call > GetEmployeeDetailsAction from jsp by passing the employee id. > In GetEmployeeDetailsAction action , u will have some thing lie this. > > EmployeeService empService = new EmpService();//u can use servuice factory > here... > EmployeeDetailsBean empDetailBean = empService.getEmployeeDetails(empId); > EmpDetailForm empDetailForm = (EmpDetailForm )form; > empDetailForm .setEmpDetails(empDetailBean ); > > return mappig.FindForward("success");// successs points to empDetails.jsp which > access the empDetailForm to render the page... > > hope this helps, > regards, > Shirish > > > > -----Original Message----- > From: kelly [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 06, 2003 11:20 AM > To: struts-user > Cc: kelly > Subject: What should and should not be in an Action class. > > > Hi All, > > I'm just trying to work out where I need to put all of my database access > code within the struts architecture. If I'm reading Craigs comments on the > Action class correctly and have got the MVC set up right, all the action > class should do is gather any necessary information, add it to the form and > then forward it on. But if I need to get data from the db and put it in the > form, should I do it in the action class or pass it to the business logic > and make the business logic forward it to the output servlet? > > I'm getting a bit confused with all this so sorry if the question's a bit > simple. > > Regards > > Simon > > Institut fuer > Prozessdatenverarbeitung > und Elektronik, > Forschungszentrum Karlsruhe GmbH, > Postfach 3640, > D-76021 Karlsruhe, > Germany. > > Tel: (+49)/7247 82-4042 > E-mail : [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
