RE: actions and business logic

Jesse -Original Message- From: Keith Bacon [mailto:[EMAIL PROTECTED]] Sent: Freitag, 8. Februar 2002 17:42 To: Struts Users Mailing List Subject: Re: actions and business logic I agree. Is it worthwhile adding a facade layer if you only have 1 or 2 different user interfaces? I can see the val

RE: actions and business logic

?WROXEMPTOKEN=34282Z8saK1uBNIvHOfBhvowLQ&type= &order=1&subject=0 Hopefully this can help you somehow. Regards, Sophia -Original Message- From: Jerome Josephraj [mailto:[EMAIL PROTECTED]] Sent: Friday, February 08, 2002 6:40 AM To: Struts Users Mailing List Subject: RE: actions

Re: actions and business logic

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

Re: actions and business logic

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

RE: actions and business logic

Mike, It's better to keep all your business logic in a separate layer say Business Services layer which is independent of your action layer. This helps you in decoupling actions and business rules. Ideally checking for rules, permissions should go in Business services layer but i

Re: actions and business logic

We also use JRF & Struts. We try never to put any business logic in the action object. Action objects call boundary objects and the boundary objects call business logic controller objects. All business logic goes into the controller objects. As you can see, we build our applications based on t