hello oliver.
what's the status here? Will you move this project to Sling?
this is not decided yet, no precise plans yet. this depends if it is useful for
a broader audience in the sling community and projects/applications built with
sling. until then just try it out from wcm.io. additionally
On Saturday 04 October 2014 01:53:38 Stefan Seifert wrote:
hi Stefan,
this proposal is about context-specific configuration, that means
configuration that cannot be stored as OSGi configurations. OSGi
configurations are always system-wide, so they are not well-suited for
storing
2) I'm assuming that the lookup key for these configuration objects is
the class name. IMHO, we need some kind of differentiator, see for
example my OAuth example earlier in this thread.
I haven't thought of this part yet, I've just stated my strong wish
for strongly typed configuration
Am 17.10.14 um 12:02 schrieb Stefan Seifert:
2) I'm assuming that the lookup key for these configuration objects is
the class name. IMHO, we need some kind of differentiator, see for
example my OAuth example earlier in this thread.
I haven't thought of this part yet, I've just stated my
Am 17.10.14 um 12:26 schrieb Stefan Seifert:
But what is the preferred way to get a configuration? I would assume
that you get a configuration for a key similar to the pid for OSGi
configurations. From an API point of view a
T[] getConfiguration(String key, ClassT type);
for a single and
hello carsten.
So I think adding an adaptTo method to Configuration might do the trick:
MyTypedConfig =
resource.adaptTo(Configuration.class).adaptTo(MyTypedConfig.class);
The adaption within the implementation of the configuration class can be
done on the fly by creating a proxy.
We should
I see 3 problems:
- allowing to hook in a custom lookup strategy and not defining a clear lookup
content model (too much magic in such things is bad, it should be obvious by
just browsing the JCR, just as with resource types)
- the idea of putting configurations itself under /content; configs
hello alex.
-Original Message-
From: Alexander Klimetschek [mailto:aklim...@adobe.com]
Sent: Tuesday, October 14, 2014 10:13 PM
To: dev@sling.apache.org
Subject: Re: [PROPOSAL] Context-specific configuration for Apache Sling,
Multitenancy
I see 3 problems:
- allowing to hook in a custom
