You can specify your own matcher in warp persist using the forAll() clause when you create a PersistenceModule.
@Inherited is really not what you want as it does not get inherited on methods annotations. Dhanji. On Wednesday, May 5, 2010, Eduardo Nunes <[email protected]> wrote: > Another key thing regarding this problem: it only happens if you compile the > application using ant (I believe it happens if you compile using JDK) instead > of eclipse. If you compile it using eclipse, no problem happens. > > Do you have an idea? > > On Tue, May 4, 2010 at 3:24 PM, Eduardo Nunes <[email protected]> wrote: > > Unfortunately it didn't work. I read the warp persistent source code and > everything looks fine there, I think the problem is in the Matcher used. I'm > not sure how it works but looks like the matcher isn't applied to the methods > of the super classes, just to the current one. > > This is the > interceptor: http://warp-persist.googlecode.com/svn/trunk/warp-persist/src/com/wideplay/warp/persist/hibernate/HibernateLocalTxnInterceptor.java it > doesn't get called on the methods declared in the super class. > > > This is the factory that creates the > matchers: http://warp-persist.googlecode.com/svn/trunk/warp-persist/src/com/wideplay/warp/persist/PersistenceMatchers.java > > > Maybe some committer of google-guice can help me to clarify those things. > Best regards,Eduardo S. Nunes > > On Tue, May 4, 2010 at 2:24 PM, Jonathan Abourbih <[email protected]> wrote: > I saw something in an earlier thread about this: > [email protected] says: > > > Annotations in java need the > http://java.sun.com/javase/6/docs/api/java/lang/annotation/Inherited.html > annotation when inheritence is required. > > > > I'm not sure if WarpPersist has defined @Transactional with that annotation, > but might be a start for you. > Jonathan > > > > > > > > > > On 4 May 2010, at 18:14, Eduardo Nunes wrote: > > Hi all, > I have a problem with warp persist. It's a inheritance problem. If a have a > class A with a method name "save" with annotation @Transactional and I have a > class B that extends A. If I call b.save it seems to ignore the > @Transactional annotation, if I do a simple method @Transactional void save() > { super.save() }; it works. > > > Do you have any idea about it? > Best regards, > -- > Eduardo S. Nunes > http://enunes.org > > > -- > You received this message because you are subscribed to the Google Groups > "google-guice" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-guice?hl=en. > > > > > > -- > You received this message because you are subscribed to the Google Groups > "google-guice" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > google-guice+unsubscr...@googlegro > > > > -- > You received this message because you are subscribed to the Google Groups > "google-guice" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-guice?hl=en. > -- You received this message because you are subscribed to the Google Groups "google-guice" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-guice?hl=en.
