If you get CotizacionManager to call ArticuloManager as a dependency, then the transaction should propagate and Spring will not start a new transaction. This does depend on the settings of the transaction manager, but I believe the default is to only start a new transaction if one is not already present.
Mike 2008/12/1 sergiovera <[EMAIL PROTECTED]> > > If a manager calls another manager, do the end up using the same > transaction, > or a new inner transaction is created? > > For example, > I have a Manager that does a lot of business rules, using several daos. Its > called ArticuloManager. > > Then, I have a new Manager, CotizacionManager, that saves a bunch of stuff, > then it should do the same actions as ArticuloManager. > I want CotizacionManager to call ArticuloManager, but because the > transactions are wired so that every Manager has its own transaction, > would > doing this (a manager calling another manager) create a new Transaction > (then I would have two transactions..just want one :sleep:) ? > > I ended inheriting CotizacionManager from ArticuloManager, but I wonder if > theres another solution. (In case one manager should call two or more > managers). > > Thanks in advance :drunk: > -- > View this message in context: > http://www.nabble.com/Appfuse-2--Manager-calling-manager--tp20774751s2369p20774751.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] > >
