On Fri, 4 Oct 2002, Billy Ng wrote: > 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?
Yes, it's a good practice. > It will be helpful if anyone can provide me samples or links for how a > business logic looks alike. It can be any common class. OK, it would be nice if it followed some simple rules like - don't accept any client specific (e.g. http related) parameters - don't expose business logic implementation details (e.g. SQL or EJB related exceptions) I recommend you EJB Design Patterns book from Floyd Marinescu (you can download it for free from www.theserverside.com), try to find something about "Business Delegate" pattern there. Pavel -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
