Many people use the Manager pattern to write their business logic.
This acts a service layer that can be used by your Struts actions, but
could also be called by other interfaces (batch processes, web
service, etc). In Appfuse these Manager classes are used to create
transactions across multiple DAOs using Springs AOP help. This way
you can pull in multiple DAOs to a single manager, do a bunch of
things and have the whole thing wrapped in a transaction.
Most Appfuse apps use com.yourcompany.service for the Manager
interfaces and com.yourcompany.service.impl for the implementations.
In the Appfuse spring configuration it will look for classes under the
package service with the string "Manager" in their name. Spring will
automatically wrap all methods for that Manager class in a transaction.
-D
On Aug 19, 2008, at 6:59 AM, krishgy wrote:
Hi All,
I have AppFuse (Basic Struts, Hibernate and Spring) project. I use
Jetty as
a web server.
I want to know where to write the business logic code outside my
Hibernate
Dao implementation?
I do not want to write the business logic in the action classes. How
to
achieve this?
Thanks in advance,
Krishgy
--
View this message in context:
http://www.nabble.com/Where-How-to-write-business-logic-in-AppFuse-tp19049163s2369p19049163.html
Sent from the AppFuse - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
