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 way to achieve that is to use an encoding scheme where by
you pass around a configuration property that holds Strings encoded as
JSON, but you have to do the work of turning that into a more complex
object perhaps using JSONP or JSONB or the Converter.

At least as David said, with Configurator it will automatically encode
complex JSON properties as Strings for you.

Just keep in mind, if the vehicle is Configuration Admin you won't have
another choice, you can't force it to work outside it's specified types.
You'll have to poor some sugar over it.

Sincerely,
- Ray

On Thu, Jul 12, 2018 at 7:53 AM, nino martinez wael <
nino.martinez.w...@gmail.com> wrote:

> Just use https://github.com/TDC-Netdesign/ManagedProperties
>
> On Thu, 12 Jul 2018, 10:55 Philipp Höfler, <philipp.hoef...@pernexas.com>
> 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.
> >
> > Raymond pointed out that I should have a look at the Configurator
> > Specification.
> > https://osgi.org/specification/osgi.cmpn/7.0.0/service.configurator.html
> >
> > I read the specification and it sounds promising.
> > But I am stuck how to use the Configuration in my project.
> > I understand that I've to add the following dependency.
> > org.apache.felix.configurator
> >
> > But I don't understand if I've to add some classes, where the json file
> > has to be placed and if it's possible to place it outside of the bundle?
> >
> > Is there any tutorial or sample project out there?
> >
> > Thanks,
> > Philipp
> >
>



-- 
*Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)

Reply via email to