Tom, I'd appreciate it if you could mock up an example; it would significantly help me better understand the various interactions between the objects and the overall concept.
Best, Dan ----- Original Message ---- From: "Clifford, Thomas" <[email protected]> To: Stripes Users List <[email protected]> Sent: Mon, November 9, 2009 2:18:07 PM Subject: Re: [Stripes-users] Where to put the logic? For writing larger apps that you need to keep the buslogic separate, I would: 1. Keep the action beans (controller?) for interacting with the user interface (presentation layer). 2. Use a service layer that takes requests from action beans, and returns what the UI needs, often dao/model objects or recordsets in the form of dao/model arraylists. You can encapsulate your business rules in this service layer, requiring neither presentation (UI) or data (dao/model) layer to know about each other. 3. Use service layer to interact with the data (dao/model) layer, keeping the UI layer From having to know about the presentation layer. I can mock up an example if you'd like.... Tom C. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
