As I don't have much to go by, I can just state some generic reasons for
this:
* The Component that feeds the Configuration to the ConfigAdmin is not
activated.
* The Configuration PID does not match the one given in the Component
annotation. If no special name is given, the full qualified Classname is
the Configuration name.
It might help if you post some code snippets with your Component
Annotation and with the part of the ConfigAdmin.
Am 24/02/2022 um 11:11 schrieb Kanika Khattar:
Hi Jurgen,
Thank you for your quick response.
For the second question, Configuration is provided via ConfigurationAdmin.
Regards,
Kanika
On Thu, Feb 24, 2022 at 2:29 PM Jürgen Albert
<[email protected]> wrote:
Hi Kanika,
all annotations that are provided by the OSGi Workinggroup (in the
name space of org.osgi.*.annotations) expect the ones for the CDI
Speci, are compile time annotations. They must be part of our
Targetplatform/ Build Dependencies and might be used by your build
tooling. This means that they are not required at runtime and
must not be deployed (which is what the failing requirement is
saying).
Regarding your second question: Do you provide a Configuration via
ConfigurationAdmin or Configurator for this Component?
Hope this helps,
Jürgen.
Am 24/02/2022 um 05:26 schrieb Kanika Khattar:
Hi All,
While using OSGI Annotations in my project, I am getting a few
issues. It will be great if you can help me with the same.
Below are the issues:
1. /!ENTRY org.osgi.service.metatype.annotations 4 0 2022-02-24
09:43:01.813
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module:
org.osgi.service.metatype.annotations [219]
*Unresolved requirement: Require-Capability:
osgi.compile.time.only;
filter:="(&(must.not.resolve=*)(!(must.not.resolve=*)))"*
at org.eclipse.osgi.container.Module.start(Module.java:463)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1845)
at
org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1838)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1781)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1743)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1665)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)
!ENTRY org.osgi.service.component.annotations 4 0 2022-02-24
09:43:01.887
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module:
org.osgi.service.component.annotations [239]
*Unresolved requirement: Require-Capability:
osgi.compile.time.only;
filter:="(&(must.not.resolve=*)(!(must.not.resolve=*)))"*
at org.eclipse.osgi.container.Module.start(Module.java:463)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1845)
at
org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1838)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1781)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1743)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1665)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)/
2. Activate method gets called when Configuration Policy is set
to OPTIONAL. When Configuration Policy is REQUIRE, the activate
method is not called.
Thanks & Regards,
Kanika
_______________________________________________
equinox-dev mailing list
[email protected]
To unsubscribe from this list,
visithttps://www.eclipse.org/mailman/listinfo/equinox-dev
--
Jürgen Albert
CEO
Chair Eclipse OSGi Working Group Steering Committee
Data In Motion Consulting GmbH
Kahlaische Str. 4
07745 Jena
Mobil: +49 157-72521634
E-Mail:[email protected]
Web:www.datainmotion.de <http://www.datainmotion.de>
XING:https://www.xing.com/profile/Juergen_Albert5
LinkedIn:https://www.linkedin.com/in/juergen-albert-6a1796/
Rechtliches
Jena HBR 513025
_______________________________________________
equinox-dev mailing list
[email protected]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
[email protected]
To unsubscribe from this list,
visithttps://www.eclipse.org/mailman/listinfo/equinox-dev
--
Jürgen Albert
CEO
Chair Eclipse OSGi Working Group Steering Committee
Data In Motion Consulting GmbH
Kahlaische Str. 4
07745 Jena
Mobil: +49 157-72521634
E-Mail:[email protected]
Web:www.datainmotion.de
XING:https://www.xing.com/profile/Juergen_Albert5
LinkedIn:https://www.linkedin.com/in/juergen-albert-6a1796/
Rechtliches
Jena HBR 513025
_______________________________________________
equinox-dev mailing list
[email protected]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/equinox-dev
