The transactions were put on the service layer to ensure that operations within a service method were atomic.
There should be no harm in putting them on the repositories also as they should propagate. I would still suggest putting it on the service. On Tuesday, June 18, 2013, Venkat (NEU) wrote: > In Rave, none of the Jpa*Repository are having @Transactional for their > save() methods. > > I have overlayed the JpaOAuthTokenInfoRepository file locally. Is this the > reason I had to add @Transactional as this is not part of the rave-jpa jar > files? Trying to find out why i had to add the annotation. > > > > > On Tue, Jun 18, 2013 at 4:24 PM, Venkat Mahadevan < > [email protected] <javascript:;> > > wrote: > > > JpaOAuthTokenInfoRepository was missing the @Transactional for save() > > method. Once I added it it worked. I will checkin the changes after > opening > > jira. > > > > > > > > > > On Tue, Jun 18, 2013 at 2:47 PM, Venkat (NEU) > > <[email protected]<javascript:;>> > wrote: > > > >> OAuthTokenInfo table is not getting populated while using an OAuth > >> gadget. Looking into it. > >> > >> > >> --Venkat > >> > >> > > > > > > -- > > -Venkat > > > > Sent via mobile device. Please excuse typos or brevity. > > > > >
