How about combining the two, and build basic superclass of CRUD, and then extends them in specific use? Just a thought.
Patrick. -----Original Message----- From: David Liles [mailto:[EMAIL PROTECTED] Sent: Monday, January 12, 2004 7:01 AM To: [EMAIL PROTECTED] Subject: design suggestion I am currently in the design phase of a project and am struggling with which way to go.... This is going to be a workflow application that allows the users to submit various request. There are several workflows that will share common functionality (list users, list organizations, etc). I'm not sure if it would be better to create action classes for each complete workflow path that contain the necessary methods to support the workflow; or to create separate action classes for each specific step of the work flow that only have method calls for CRUD functions (create, read, update, delete) and chain them together to create the work flow path based on some type of work flow attribute. Each work flow requires a "next step" and "previous step" button so the user can either continue with their request or navigate back to make changes to information in a previous step in the flow. Needing this type of functionality, I'm not sure which solution would be best.... Any suggestions? Thanks - Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
