Would you mind referring to the section you are referring to specifically
by number and paragraph number just so we can better orient ourselves? We
don't read these every day so we often forget what's there.

:)

Sincerely,
- Ray

On Mon, Nov 21, 2016 at 2:21 PM, Balázs Zsoldos <balazs.zsol...@everit.biz>
wrote:

> Hi,
>
> I read about the new features of ConfigurationAdmin that will be applied
> in the new OSGi release. After checking the new functions, I feel that I
> might miss the point.
>
> What I feel that the new functions have no other purpose but satisfying
> some of the requirements of Apache Felix FileInstall.
>
> It is possible to create factory config instances, but it is not possible
> to do it with any kind of pid. That somehow does not make sense to me. Why
> not all of them just some of them?
>
> Why is the special character the hashmark? Is it because Felix ConfigAdmin
> uses a dot at the moment? What about other implementations of the
> specifications? Or the new versions of specifications are written based on
> the current implementation specific details? Even if almost everybody uses
> the Felix implementation.
>
> I think that a universal solution would help much more projects, not only
> Config Admin. By an universal solution, I mean: Possibility to deploy
> configurations with pre-defined pids. This could be a help for FileInstall,
> too.
>
> With a universal solution, use-cases could be solved without workaround
> like:
>
>    -  Deployment of configurations from source-control at development
>    time: Imagine that we use an IDE that supports starting OSGi containers,
>    keep the config with the sources and update configuration without
>    restarting the OSGi container
>    - Deployment of configuration to several computers in a clustered
>    environment
>
>
> What do you think? Am I missing the point?
>
> *Balázs **Zsoldos*
>
>
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev
>



-- 
*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)
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev

Reply via email to