While I haven't (yet) had this opportunity, I can't wait until the day that I wrap service interfaces with Web Services and connect it to a mobile UI.
For that case alone, I focus my strategy on Spring managing the transaction with load-time weaving. $0.02... On Aug 30, 2010, at 10:31 PM, Alexander Morozov wrote: > > Brain thank you for comment, > > saying about Wicket and transactions, from my point of view, we have 2 > posibilities: > 1. manage transaction boundaries on per-request way (override > RequestCycle.onBeginRequest(), RequestCycle.onEndRequest(), > RequestCycle.onRuntimeException()) with PlatformTransactionManagement (do > not forget to proper configure TM with > SYNCHRONIZATION_ON_ACTUAL_TRANSACTION) > 2. propagate transaction by means of AspectJ and load-time weaving for > "actionable" wicket subtypes (such as IFormSubmitListener, ILinkListener and > etc.) > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/OT-Best-practices-regarding-service-layers-DAOs-tp2400408p2400954.html > Sent from the Wicket - 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]
