This article shows somewhat what I want although a light weight approach would be a little more nice: http://jpz-log.info/archives/2010/02/11/revisiting-guice-and-aop-with-aspectj/
Don't need all the heavy weight AspectJ.. I might do something simple like having 2 annotations before and after which then takes an @named annotation as param for the method to call.. regards Nino 2011/9/20 nino martinez wael <[email protected]>: > I wonder if this i more a guice question. So are there somone who already > have done the boiler plate and made something like i describe below? > > ---------- Forwarded message ---------- > From: "nino martinez wael" <[email protected]> > Date: Sep 16, 2011 2:19 PM > Subject: Guice/Interfaces & impl AOP like? > To: <[email protected]> > > Hi > > I use the annotated approac alot, but sometimes it would be very > helpful if I pass on some logic. > > Heres a little example: > > DaoInterface > > @Select(value="select * from contractors") > @Implementation(class=BusinessLogic.class. method="contractorlogic") > public List<Contractors> getContractors() > > > BusinessLogic > > public List<Contractors> getContractors(List<Contractors> list){ > //Do businessLogic > return list; > } > > Heres the call chain I want: > > DaoInterface.getContractors()->BusinessLogic.getContractors(List<Contractors>)->DaoInterface.getContractors() > and done... > > > And of course its the otherway around on update statements, I guess > @preprocess and @postprocess are also possible names.. > > Is something like this possible, or should I just go dig up guice(now > im thinking of it, it's more naturally a guice lib) lib for it? > > Regards Nino > -- 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.
