Hi By default it’s based on component name.
But you can provide any pid. Metatype is enabled by default in Karaf. So, you can have your annotation @ObjectClassDefintion. However, you can’t mix SCR level property and metatype property. So it’s all one or the other. Regards JB > Le 4 juin 2020 à 14:49, Christian Lutz <christianl...@kreeloo.de> a écrit : > > Hello JB, > > oh it is wired to the name of the component. I will give it a try. > > If I look into the OSGI compendium ObjectClassDefinition is a MetaType > Annotation. What did I miss? > > Kind regards > Christian > >> Am 04.06.2020 um 14:44 schrieb Jean-Baptiste Onofre <j...@nanthrax.net>: >> >> And by the way, you can also use metatype. >> >> Regards >> JB >> >>> Le 4 juin 2020 à 14:38, Christian Lutz <christianl...@kreeloo.de> a écrit : >>> >>> Hello, >>> >>> is it possible with karaf (4.1.x or 4.2.x) to use a configuration file with >>> an ObjectClassDefinition? >>> >>> E.g. I have a simple ObjectClassDefinition with one boolean method. I set >>> the pid property to de.xy >>> >>> My idea was that if I want to change the default value all I need to do is >>> to create a de.xy.cfg file in karaf /cfg set the boolean value to false and >>> during the component active the value from the config file will be used >>> instead of the default value. >>> >>> I found some tutorials of how to use the objectclassdefinition itself. But >>> I didnt find anything about how I am able to wire this with the karaf >>> Configuration Admin Service. >>> >>> Kind regards >>> Christian >> >
