We put them on CASImpl because technically that is where the transaction would occur (a single method on that class could call multiple ticketregistry methods) On May 30, 2014 3:00 PM, "Marvin Addison" <[email protected]> wrote:
> > I think the > > underlying problem in the code is that @Transaction annotations were > > placed at the wrong layer, on the methods in class > > CentralAuthenticationServiceImpl. > > +1 > > Your analysis and solution are probably the best evidence we have for > that claim. I recall having made a similar suggestion in the past, but > I didn't have a sound argument at the time. I believe your problem and > solution provide the evidence we need to move forward with a fix in > the next release of CAS. I would appreciate your filing a Jira issue > to make the change you suggested and citing this thread as a > reference. > > Thanks for your persistence working through this issue and sharing the > result. Hopefully it will lead to a fix for this long-standing issue. > > M > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
