Mea culpa! Actually, I cannot confirm my report, I refactored code many times... and now interception methods with annotated arguments works well. Sorry.
But in cases specified in documentation<http://code.google.com/p/google-guice/wiki/AOP#Limitations> would be nice to see some warnings from Guice in console... Thanks, and sorry again. On Friday, October 19, 2012 4:04:25 PM UTC+2, Martin Schayna wrote: > > Hi, > > I have app based on Jersey REST server and now I'm trying to use > guice-persist. I could not use guice-persist as is, but I borrow some > thoughts, esp. transaction control via @Transactional annotation and method > interceptor. But I found some glitches, which are guice specific. > > This method is OK and method interceptor is invoked: > > @Transactional > @Path("/ok") > *public* String ok() { ... } > > > but for this one interceptor is not invoked: > > @Transactional > @Path("/fail/{id}") > *public* String fail(@PathParam("id") String id) { ... } > > > So annotatated arguments prevents method intercepting. When I annotate > arguments in interface and than implement this interface (which is > thankfully supported in Jersey), it works. I think that this limitation is > not specified in docu > http://code.google.com/p/google-guice/wiki/AOP#Limitations > > Can I see warnings or so for methods which Guice should intercept (i.e. > matches binding matchers) and could not due limitations? It seems like > lotery to me... > > Thank you! > > -- You received this message because you are subscribed to the Google Groups "google-guice" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-guice/-/XiHYar4pSIwJ. 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.
