> -----Original Message----- > From: James Carman [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 13, 2006 12:42 AM > To: 'Tapestry users' > Subject: RE: tapestry-hibernate integration problem > > > Anything which really wants to update the persistent objects > should go on > inside a service method. Then you can put the transaction > interceptor on > it.
I disagree. When you work directly on your domain model, you only have to commit. Even in Tapernate, when you persistence strategy loads an entity from its id, you can just let tapestry change properties and commit them. What service method do you call in addition? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
