|eZ Publish core configuration is prefixed by ezsettings namespace, while internal configuration (not to be used directly) is prefixed by ezpublish namespace.|
Note that using semantic configuration is better than normal service configuration.
You will learn about it in the Cookbook on How to expose a semantic configuration for a BundleFor configuration that is meant to be exposed to an end-user (or end-developer), it's usually a good idea to also implement semantic configuration.
Note that it is also possible to implement SiteAccess aware semantic configuration.
parameters: myapp.parameter.name: someValue myapp.boolean.param: true myapp.some.hash: foo: bar an_array: [apple, banana, pear]
Inject the ConfigResolver in your services
Instead of injecting the whole ConfigResolver service, you may directly inject your SiteAcinject your SiteAccess aware settings (aka dynamic settings) into your own servicescess aware settings (aka dynamic settings) into your own services.
You can use the ConfigResolver in your own services whenever needed. To do this, just inject the