This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
In struts, an Action class is subclassed to act as a controller. In the jsp page, it needs to display many records (obtained from database). I am now thinking which method in the following 2 cases is better: 1) call the session bean in the subclass of Action class 2) the jsp page calls a javabean which call the session bean Which method is better for the performance? In the code, it seems that it is better for the case 1, because the jsp page does not need to deal with the business logic. However, in case 1, after the Action obtained the data, I need to use this code: request.setAttribute("...", theObject). Thanks! Stephen Lee
As Tim says, you'll probably not notice any performance difference whichever you choose. From an architecture/design perspective, since you're using a Model-2 framework, you're better off accessing the session bean functionality from your Action class for increased reusability, maintainability, etc. Cheers Simon