The practice I've done, and seen done, is to call your business logic from the action. Take the form/whatever from the Action, change it into a DO/VO/POJO and pass it off. The business logic can be in a local class, or it can call an EJB (stateful/stateless). This keeps the business logic modular and reusable without being locked into a presentation form.
The business logic can throw errors, populate a List with errors and hand it back to the Action. (Don't forget -- the view layer has some logic: it's display logic, not business logic). The action can then redirect the user based on the return (or lack) of errors.


hth.

--- adam



From: Bill Johnson <[EMAIL PROTECTED]>
Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Business logic goes where in MVC/Struts??
Date: Wed, 16 Jul 2003 10:48:37 -0700 (PDT)

I'm curious where the business logic is supposed to go
when programming MVC/Struts.  In Struts' case it
shouldn't go in Action object right?  Business logic
is considered to be part of Model right?

Regards,

Bill

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

_________________________________________________________________
The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to