I am getting error when I deploy mvn project . Non annotation type for activation object with descriptor (Lcom/xxx/sss/ssss;)V, type xxxxx -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal biz.aQute.bnd:bnd-maven-plugin:5.1.2:bnd-process (bnd-process) on project xxxxxx: Non annotation type for activation object with descriptor
Solved! Go to Solution.
Views
Replies
Total Likes
With this being fixed, config service is not automatically bounded. I have to manually open and bound it in OSGi config manager.
I have immediate =true in the class
Views
Replies
Total Likes
Can you share the java class where you have this issue?
Here is my interface
Here is my Service Impl
This is based on https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/developing/osgi-servi...
Views
Replies
Total Likes
It seems the above code is fine but whenever I try to use this in some class like
@component(service = SomeOtherService.class, immediate = true)
public class SomeOtherServiceImpl implements SomeOtherService {
@reference // Or even @OSGIService
private ProviderABCConfigService providerABCConfig;
it returns
Non annotation type for activation object with descriptor (Lcom/xyz/aem/service/ProviderABCConfigService;)V, type com/xyz/aem/service/ProviderABCConfigService
Views
Replies
Total Likes
Can you check the java import type also. e.g.
https://github.com/arunpatidar02/aem63app-repo/blob/master/java/AuthorFeature.java
Views
Replies
Total Likes
It was my mistake, in the other OSGi class SomeOtherServiceImpl I have
// @activate
// protected void activate(ProviderABCConfigService config) {
//
// this.xyzConfig = config;
//
// }
This was causing the issue, as soon as I comment this build worked fine.
Thanks for your help
Views
Replies
Total Likes
With this being fixed, config service is not automatically bounded. I have to manually open and bound it in OSGi config manager.
I have immediate =true in the class
Views
Replies
Total Likes
Views
Likes
Replies