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 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 <[email protected]> > wrote: > > 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 this see SLING-6305 [1], where the > > LoginAdminWhitelist config is applied too late. > > > > Top of my head, some (probably bad) ideas are: > > > > 1) Make the component require a configuration > > > > This makes the component less flexible and we should aim for a > > minimal > > configuration with Sling. > > > > 2) Post-process the configurations using the slingstart-maven- > > plugin > > and adjust the configurationPolicy to be > > ConfigurationPolicy.REQUIRED > > > > This is a bit suprising and makes it harder for components to be > > switched to a default configuration after being provisioned. > > > > Suggestions would be greatly appreciated :-) > > > > Thanks, > > > > Robert > > > > > > [1]: https://issues.apache.org/jira/browse/SLING-6305
