Re: @Component and @AspectService not playing nice

Hi Steve, You are correct. I just checked, and indeed, what you are describing can be done using the DM api, but it's not supported when using annotations. As a work around, you can do the following: in your SomeDomainSpecificClass aspect implementation, you can manually register the aspect

Re: @Component and @AspectService not playing nice

Pierre, Thanks for the solution. My goal is remove boilerplate in our system by ditching activators where possible, using the annotations. This solution, while slightly manual, is a major step in the right direction and might be automatable using inheritance.

Re: @Component and @AspectService not playing nice

AspectComponent = getDependencyManager().createAspectComponent().setAspect(SomeDomainSpecificClass.class, null, 10) component.setInterface(EntitySynchronizer.class, properties); component .add(getDependencyManager() .createServiceDependency()

Re: @Component and @AspectService not playing nice

Hello Steve, These annotations are part of the Felix DependencyManager (DM) annotaitons. So, the two annotations can't be mixed. @AspectService are specialized DependencyManager components (like @AdapterService, or @BundleAdapterService), and can be used to dynamically define an interceptor (or

Re: @Component and @AspectService not playing nice

Thanks for the responses. >From what I am reading out usage where we have services that are both >interceptors (aspects) and services (in their own right) that are white >boarded in is atypical. I could probably work around this by adding service >properties (or use one of the ones we are