What you are reading about is the MVC pattern. The reason to not code your logic in the Action is that you are now locking the application into a web world. You can't reuse that logic in a non-Struts way at all. By encapsulating your Logic in its own class, you break that dependency.
Here is one link on MVC, there are hundreds: http://www.uidesign.net/1999/papers/webmvc_part1.html Some things this will force you into doing the "right" way: Handling generic errors from the business layer and wrapping them in the ActionError. Instead of doing that in the business layer. It should also force you to use ActionForms for the View layer, but use a business domain data object for the model layer. Hopefully this is a decent pointer, otherwise let me know. Good luck. Scott From: Billy Ng <[EMAIL PROTECTED]> Subject: Business Logic Bean Question Date: Fri, 4 Oct 2002 10:27:20 -0700 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C26B90.9F265F70" Hi folks, I have been reading some articles briefly talking about the business logic beans. The way I build my Struts app is to use the Action's perform or execute method to do the business logic. Then, I set the data into a bean and pass it off to the JSP. It works just fine. However, my question is if I should do the business logic in Action? Am I supposed to hand down the job to a business logic bean? It will be helpful if anyone can provide me samples or links for how a business logic looks alike. Thanks in advance! Billy Ng __________________________________________________ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
