It's really hard to tell without knowing what kind of struts-based web application you are designing.
You might want to find out what service components you will lookup and/or create, and how often are these operations. Struts handles action dispatch pretty well. (On a side note, I am not sure why the creator of Struts once mentioned on this mailing list that Struts are meant to be a front-controller; that it resides in the presentation tier mainly. For me, anything after ActionMapping belongs to business tier). It makes my head hurts to think of all this the late of the day:). -----Original Message----- From: John Boyes [mailto:[EMAIL PROTECTED] Sent: August 7, 2003 3:40 PM To: [EMAIL PROTECTED] Subject: Service Locator pattern useful if not using EJBs? I'm currently deciding on which design patterns to use for a Struts-based web application. Definitely going to use a Business Delegate to ensure a proper separation of the business and presentation tiers. Is it good practice to use a Service Locator to look up services for the Business Delegate? I can see the benefits of using a Service Locator when using EJBS, however I'm not going to use EJBs. Are there any other pertinent benefits in using a Service Locator, or is it an unneccessary extra level of complexity in a non-EJB implementation? Any replies much appreciated, John --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
