On Fri, Nov 21, 2014 at 9:54 AM, Thiago H de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Fri, 21 Nov 2014 12:50:11 -0200, George Christman <
> gchrist...@cardaddy.com> wrote:
>
> I tried those Lance with the exception of @CommitAfter do to the fact I
>> thought that @CommitAfter needed to
On Fri, 21 Nov 2014 12:50:11 -0200, George Christman
wrote:
I tried those Lance with the exception of @CommitAfter do to the fact I
thought that @CommitAfter needed to be used in the interface.
Before the latest 5.4 betas yes, but not anymore.
I even went as far as passing the save off to
I tried those Lance with the exception of @CommitAfter do to the fact I
thought that @CommitAfter needed to be used in the interface. I even went
as far as passing the save off to my DAO that has been configured to use
HibernateTransactionAdvisor. I thought for sure this would resolve the
issue, bu
@CommitAfter will only work on service methods if you applied the
HibernateTransactionAdvisor or HibernateTransactionDecorator to the
service.
On Fri, 21 Nov 2014 06:47:43 -0200, Lance Java
wrote:
I'm guessing you need to commit a transaction.
Either:
HibernateSessionManager.commit()
I'm guessing you need to commit a transaction.
Either:
HibernateSessionManager.commit()
Or:
Session.getTransaction().commit()
Or:
@CommitAfter
