The goal of keeping business logic out of action classes (IMHO) is to increase the reusability of the logic. Based on this, I would say it depends on how you use your value / logic / config beans on your non-web-based applications (if any). Or, how you would use them if/when you went to build other (non-web-based) applications.
Have foresight. Think of how you can make the most out of what you are going to write. Have as your end goal reusability. Build everything on that precept. No, you can't reuse everything you write, but the goal is to maximize code reuse. HTH, Eddie ----- Original Message ----- From: "Phase Web and Multimedia" <[EMAIL PROTECTED]> To: "Struts User List" <[EMAIL PROTECTED]> Sent: Tuesday, April 30, 2002 12:50 PM Subject: Best Practice Question. > I have a bean that is created when my app starts and it contains some > database table conifguration info (I'll call it my config bean). Later on in > an Action class another bean, that I'll call my logic bean, needs to access > the values of the config bean. Would it be proper to use the Action class to > pass the config bean to the logic bean and let the logic bean extract the > values or should I extract all the values from the config bean within the > Action class and pass the config info in a different manner. > > Thanks, > Brandon Goodin > Phase Web and Multimedia > P (406) 862-2245 > F (406) 862-0354 > [EMAIL PROTECTED] > http://www.phase.ws > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
