The problem may be caused by overriding of generic methods and/or by the Spring AOP transactional advice. A few things to try/check:
1) Make sure that when you extend GenericManagerImpl you specify a type for the generic parameter: xxxManagerImpl extends GenericManagerImpl<xxx,Long> as an example. 2) Add the @Override annotation to the method in the xxxManagerImpl to make sure it really is overriding the method from GenericManagerImpl. 3) Make sure the interface for xxxManagerImpl extends the interface GenericManager and sets a type as above. 4) If all that fails, have you tried declaring the method in the interface for xxxManagerImpl? Mike. On 6/19/07, arvinder <[EMAIL PROTECTED]> wrote:
I am getting data failure exceptions if I try to override GenericManager methods. As an example, If I try to override save method of GenericManagerImpl in my xxxManagerImpl I get a Data access failure error about transaction being read only. This error occurs even if I have only one line of code, return super.save(object). But if I create a custom method saveXXX(object) in my xxxManagerImpl and call super.save(object) from that, every thing works fine. Is it the default behavior in Appfuse 2M5? Does this apply to DAO's too? Thanks. -- View this message in context: http://www.nabble.com/Data-Failure-Error-on-overriding-Generic-Manager-methods-tf3945744s2369.html#a11192760 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
