Re: Configurator R7 example

Hi Martin, It’s refreshing to see so much enthusiasm! I wonder if you might provide a valuable service to your current and potential users by providing a detailed comparison of capabilities compared with the R6 and R7 specs, and possibly also including felix DS extensions such as

Re: Configurator R7 example

Hi David I started managedproperties before tjat specification was finished and i havent really used it, as ManagedProperties has been my goto configadmin communication method. I will highlight the main functions of it, but i cant say if DS can do it too now. But the advantages are: The

AW: Configurator R7 example

Thanks for your very detailed explanation. If I got you right, with ManagedProperties I am not bound to the primitives the default osgi implementation provides, but I can use any Java type. Up to now, I think I am fine with factory configuration, but probably I come back to you in a few weeks,

Re: Configurator R7 example

Hi Martin, I guess you are the developer of this ManagedProperties? How does it differ in capabilities to the configuration-by-annotation that is built into DS 1.3? thanks david jencks > On Jul 12, 2018, at 10:53 AM, Martin Nielsen wrote: > > Hello everyone > > I saw ManagedProperties

AW: Configurator R7 example

I didn't get the point of factory configurations until I read your explanation - thanks. I think this is exactly what I was looking for. I'll try it tomorrow ... -Ursprüngliche Nachricht- Von: Raymond Auge Gesendet: Donnerstag, 12. Juli 2018 18:23 An: felix users Betreff: Re:

Re: Configurator R7 example

Hello everyone I saw ManagedProperties mentioned so now I appear! @Philipp.Hoefler if what you mean by complex types is that you want the configuration admin to return some more advanced types like URLs Files or Dates, then ManagedProperties will handle that for you. If not then stop reading:)

Re: Configurator R7 example

On Thu, Jul 12, 2018 at 11:58 AM, Philipp Höfler < philipp.hoef...@pernexas.com> wrote: > Right, this is missing. > I added the @RquireConfigurator annotation to the GoGo Command class. Is > that a suitable place for it? > The json is now being loaded. The value is set to false. > > Could you

AW: Configurator R7 example

Right, this is missing. I added the @RquireConfigurator annotation to the GoGo Command class. Is that a suitable place for it? The json is now being loaded. The value is set to false. Could you please explain, how this is working? It's not completely clear to me, why the @interface MyConfig is

Re: Configurator R7 example

Did you add the requirement to your configuration bundle? Require-Capability: osgi.extender; \ filter:="(&(osgi.extender=osgi.configurator) \ (version>=1.0

AW: Configurator R7 example

Hallo David, thanks for the explanation. So, the configurator is just a "wrapper" for the ConfigAdminService to read json and transfer it into a key value format, right? I still have problems to use the I put a test.json file in the OSGI-INF/configurator folder of a bundle with the following

Re: Configurator R7 example

Nino, DS has that build in with Component Property types. I'm not sure that's quite what the OP is asking. If I'm not mistaken I think what Philipp is asking for is the ability to have types which go beyond the types defined in Configuration Admin (or for Service Properties). I think the only

Re: Configurator R7 example

Just use https://github.com/TDC-Netdesign/ManagedProperties On Thu, 12 Jul 2018, 10:55 Philipp Höfler, wrote: > Hi, > > I am searching for a possibility to load complex configurations. > I tried the ConfigurationAdminService, but key value pairs are not > sufficient as I need complex types. > >

Re: Configurator R7 example

Hi Philipp, In the end the configuration specified with the Configurator will end up in OSGi Configuration Admin, so the Configurator is limited to the same types as ConfigAdmin. The Configurator allows complex JSON values to be specified, they will end up as JSON text in Configuration Admin if

Configurator R7 example

Hi, I am searching for a possibility to load complex configurations. I tried the ConfigurationAdminService, but key value pairs are not sufficient as I need complex types. Raymond pointed out that I should have a look at the Configurator Specification.

GoGo Shell not accessible

Starting some days ago, the GoGo shell is gone crazy and prints something like this: INFORMATION: Setting the server's publish address to be / 13:04:30.451 [main] DEBUG org.apache.aries.jax.rs.whiteboard.internal.Whiteboard - Registered endpoint g! g! g! g! g! g! g! g! g! g! g! g! g! g! g! g!

Re: [ANN] Felix Logback version 1.0.0 Released

One more thing: my use cases compel me to use config admin because I have to support configuration filters. These can expand certain tokens into absolute paths, or map properties to environment variables or even encrypt certain keys. So it may be valuable to find a way to configure out of

Re: [ANN] Felix Logback version 1.0.0 Released

Configuring loggers through ConfigAdmin creates a bootstrap problem: You won't get logs until ConfgAdmin is up. It however can also log. Even if this is not the case you have to find a way to handle logs in the window between framework startup and log configuration. One way is to do an initial

Re: How to investigate a "Unsatisfied" reference with felix.scr ?

On Thu, Jul 12, 2018 at 2:01 AM, Cristiano wrote: > Hi Neil, > > yes, it was the output from felix scr:list command. > > Take a look at the bundles loaded in PDE below. > > idState Bundle >> 0ACTIVE org.eclipse.osgi_3.13.0.v20180409-1500 >> Fragments=18 >> 1