Return-Path: Delivered-To: apmail-jakarta-struts-user-archive@apache.org Received: (qmail 66273 invoked from network); 1 Apr 2002 20:57:10 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 1 Apr 2002 20:57:10 -0000 Received: (qmail 9216 invoked by uid 97); 1 Apr 2002 20:57:00 -0000 Delivered-To: qmlist-jakarta-archive-struts-user@jakarta.apache.org Received: (qmail 9178 invoked by uid 97); 1 Apr 2002 20:57:00 -0000 Mailing-List: contact struts-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Struts Users Mailing List" Reply-To: "Struts Users Mailing List" Delivered-To: mailing list struts-user@jakarta.apache.org Received: (qmail 9167 invoked from network); 1 Apr 2002 20:56:59 -0000 Message-ID: <3CA8C9C1.10508@interlink.net> Date: Mon, 01 Apr 2002 15:57:37 -0500 From: Neil Pitman Reply-To: npitman@interlink.net Organization: 2953734 Canada Inc User-Agent: Mozilla/5.0 (Windows; U; Win98; en-CA; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1 X-Accept-Language: en-ca MIME-Version: 1.0 To: Struts Users Mailing List Subject: Re: Is this ok architecture for struts? References: <13213878441.20020329175835@reumann.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Rick, I am a newbie. What is the motivation to having two business objects? Is BO-II just a wrapper for use cae specific behavior? or does it have all the business logic and leave BO-I as a just the physical DB work? Could this be expressed in EJB terminology? Rick Reumann wrote: > I'm wondering if this a decent design architecture for a non-EJB web > application using Struts. I'd appreciate any comments or advice. (Does > it break any J2EE principles or not follow any, etc.) For this small > example, this architecture is just for wanting to display a list of > employees in a JSP page: > > BusinessDB Object I > - database query returns ArrayList of EmployeeBean objects (these > EmployeeBean objects have different datatype members other than > String). > > Business Object II > - makes call to above Buisness1 Object to get the ArrayList of > EmployeeBeans. Now iterates through this List and makes > a new ArrayList of EmployeeForm objects that have proper String > representations of the EmployeeBean datatypes (ie- birthDate > in 08/11/1969 format, double salary in currency format, etc). > > EmployeeAction Object (using EmployeeForm object ) > - typical struts action. Makes call to above Business object to get > ArrayList of EmployeeForm objects and puts them into the request or > session > > JSP > use iterate tag and bean tag to display the EmployeeForm properties > > > -- > > Rick > > mailto:maillist@reumann.net > > "Any man, in the right situation, is capable of murder. But not any > man is capable of being a good camper. So, murder and camping are not > as similar as you might think." > -Jack Handey > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > > -- Neil Pitman npitman@interlink.net +1.514.863.5465 -- To unsubscribe, e-mail: For additional commands, e-mail: