On Mon, 2016-11-21 at 20:04 +0530, Chetan Mehrotra wrote:
> On Mon, Nov 21, 2016 at 7:01 PM, Robert Munteanu
> wrote:
> > Maybe you can suggest the correct value of the
> > sling.installer.requiredservices framework property for a service
> > with
> > a given PID
>
> From test case case it looks
On Mon, Nov 21, 2016 at 7:01 PM, Robert Munteanu wrote:
> Maybe you can suggest the correct value of the
> sling.installer.requiredservices framework property for a service with
> a given PID
>From test case case it looks like following framework property should work
sling.installer.requiredserv
On Mon, 2016-11-21 at 14:14 +0100, Bertrand Delacretaz wrote:
> On Mon, Nov 21, 2016 at 11:25 AM, Felix Meschberger om> wrote:
> > ...I assume you have a provisioning problem in that the bundles are
> > started and
> > thus the components activated *before* the configuration is
> > actually stored
On Mon, 2016-11-21 at 10:25 +, Felix Meschberger wrote:
> Hi
>
> I suggest to attack the problem at the right place !
>
> When Configuration Admin is active and configuration is stored in
> Configuration Admin, then configuration *is* provided as soon as such
> components are activated. If no
Right, but I have no idea how to apply the fix after reading the issue
description :-)
Maybe you can suggest the correct value of the
sling.installer.requiredservices framework property for a service with
a given PID?
Thanks,
Robert
On Mon, 2016-11-21 at 15:53 +0530, Chetan Mehrotra wrote:
> I
On Mon, Nov 21, 2016 at 11:25 AM, Felix Meschberger wrote:
> ...I assume you have a provisioning problem in that the bundles are started
> and
> thus the components activated *before* the configuration is actually stored
in Configuration Admin
I also think configurations should be active ve
Hi
I suggest to attack the problem at the right place !
When Configuration Admin is active and configuration is stored in Configuration
Admin, then configuration *is* provided as soon as such components are
activated. If not, this is an SCR bug.
Now, I assume you have a provisioning problem in
I think this issue should have been fixed with SLING-5779. May be the
new config that is exposed needs to be enabled for out of the box
Sling setup?
Chetan Mehrotra
On Mon, Nov 21, 2016 at 3:50 PM, Robert Munteanu wrote:
> Hi,
>
> I think we have an ongoing problem with components that:
>
> - ar
Hi,
I think we have an ongoing problem with components that:
- are defined with ConfigurationPolicy.OPTIONAL
- have a configuration defined in the provisioning model
What can happen is that the component is activated, is referenced and
used, and at a later time is configured.
For an example of
