I agree. Is it worthwhile adding a facade layer if you only have 1 or 2 different user interfaces? I can see the value if a change to business logic requires dozens of GUI changes. Also if you are writing a UI for a part of a complex system it's a way of the owners of the system presenting you with a restricted/simplified interface.
For workflow some people seem to want to specify it with tags on the jsp, but I prefer (as you say) to do it in the action class. The jsp page is concerned with display/capturing data job not where it's going to or coming from. These insights into how othe people things are fascinating & valuable - more please! Keith. --- [EMAIL PROTECTED] wrote: > > Hi! > > In my opinion: > > The Action-objects should handle the workflow, second level validation, > security, ... and so on. It makes things much more complicated when you mix > up workflow with business logic. So usually I try to use a facade pattern > (see design pattern book from gang of 4) for getting a high level > abstraction of my business logic and a central access point for my action > layer! Additionally reusability and maintenance is also an important > factor. By means of a facade pattern you are more fexible if you have to > change the business logic. And if there is no bl in your action classes it > is easier to change the workflow! > > Chris. > > > > > > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > __________________________________________________ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
