Depends what you want. Remember in OSGi, the same bundle can be used in multiple "applications". When you write a web app, all the jars you use are inside your web app and another web app won't use your jars. That's not the case in OSGi, so if you want an application to use some AOP on a given bundle, the effect would be global. That could be a problem too. So knowing who is the requester can have some value. And service hooks can provide that afaik.
On Wed, Mar 31, 2010 at 11:29, Guo Du <[email protected]> wrote: > On Wed, Mar 31, 2010 at 10:12 AM, Guillaume Nodet <[email protected]> > wrote: > > Wouldn't it make more sense to use service hooks instead ? > > The current design is limited as if a user wants to grab the list of > > services and use those, that would not work. > >> > Option 2 is intercepting the calls and dynamically weaves in > >> > code...something akin to asm bytecode weaving? > The approach looks like some kind of hacking. For proper AOP :) the > service should be intercepted in first place before publish. > > -Guo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
