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.
I have an Employee Mangement application which does the following functionality 1. Add Employee 2. Edit Employee 3. Delete Employee 4. List Employees.
The flow of the appln is as follows : 1. Login to the Application 2. List Employee Screen displayed 3. From List Employee Screen Add,Edit/Delete Employee is possible.
My requirement is that I want a single form class to hold all Employee data (Emp Id, Name, Addr) which can be used across all screens. I encountered an issue while coding this form class - The Delete Employee screen requires only the Emp Id form-property,so I had to create a new form class for that screen exclusively. I found that there is duplication of form beans. Is there a better approach in Struts than creating separate form classes for every screen?