Hi Frederik, The way to get interceptors involved in Blueprint is to add a namespace handler. This is something that processes a blueprint namespace extension. So you would define a namespace that you would add to blueprint, and maybe an associated element that you would include to identify the services to be intercepted, and then your namespace handler would be engaged and have the opportunity to do its work.
Apache Aries has a number of examples of this (e.g. JPA, Transactions). I'd probably start by taking a look at the one for transactions: https://svn.apache.org/repos/asf/aries/trunk/transaction/transaction-blueprint/ I hope this helps. Regards, Graham. On 10 November 2011 06:48, De Backer Frederik (DBB) <frederik.debac...@dexia.com> wrote: > Hello all, > > I am wondering if the OSGi Enterprise specification has some support to > define interceptors on OSGi service methods. Suppose for example that I want > to log the request parameters of a method, is it possible to define an > interceptor in the blueprint.xml method on the service definition. I guess > not because I haven't found anything until now. Is there some recommended > approach to implement this? For example, by using an AOP framework like > aspectj or using spring annotations (however in the last case I don't how > how it is possible to define the annotations since I would need another > spring-beans.xml file to define my annotations, next to my blueprint.xml > file). Has someone done any work on this? > > Thx a lot for the assistance and kind regards, > > Frederik. > > ------------------------------------------------------------------------- > Dexia disclaimer: > > http://www.dexia.com/maildisclaimer.htm > ------------------------------------------------------------------------- > >
