On 7/8/07, Dale Newfield <[EMAIL PROTECTED]> wrote:
cdtm wrote:
> I have a manager that gets some data from another source (via notification).
> Upon reception of an event this manager has to update user information.
So tell spring to inject the userDao into your other manager, and make
calls to it.
Since the manager method boundary is the transaction boundary, one
manager really shouldn't call another one, but rather all manager
methods should deal directly with the daos to get their work done. A
manager can have any number of daos available, as long as the manager
has the appropriate setters, and tells spring to provide the instances.
It should be OK to call one manager from another - especially so you
don't have to duplicate business logic or add another AOP pointcut.
The transaction boundaries are PROPOGATION_REQUIRED, which means
"participate in a transaction if one exists, otherwise, start a new
one".
Matt
-Dale
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
http://raibledesigns.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
