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 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 my DAO
>>
>
> What would be the point of having a DAO if your business rules classes
> used Hibernate directly? :)
I have a generic dao I use for my entire application that is
configured with HibernateTransactionAdvisor. I wasn't aware of the fact you
can now use @CommitAfter in the impl in 5.4, so I figured passing the save
off to my DAO would overcome the HibernateTransactionAdvisor issue.
>
>
> that has been configured to use HibernateTransactionAdvisor.
>>
>
> Have you tried to your business rules service too? No, how can you
> use @Match("*DAO") on multiples? Maybe one on "*Impl" ?
>
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
--
George Christman
CEO
www.CarDaddy.com
P.O. Box 735
Johnstown, New York
