Lets continue this discussion later. As I need it only for the builder
extension I will add this as SPI interface to the extension modules.
WDYT?
Oliver
Am 12.02.15 um 17:45 schrieb Anatole Tresch:
Basically I was thinking of something similar in my original code, called a
metamodel. But looking at our model, this is basically nothing else than a
PropertySourceProvider. You can do whatever is appropriate there. For
further isolation of you can then implement ConfigurationProvider, so the
current API is more than flexible enough. Wwe could add such features as
part of an extension (which I would find useful as well). And since I dont
want to duplicate resource locating code and the parsing logic, I am
working on the resources and formats module...
But the overall point is that the API is still flexible enough IMO.
Oliver B. Fischer <[email protected]> schrieb am Thu Feb 12 2015 at
16:57:22:
To complicated. I miss this feature and discussed it with my colleagues
at Deutsche Post. Their and my opinion is that without this
functionality Tamaya wouldn't fit to our infrastructure.
I knew all of our users could extend one of the existing property
providers but I think this shouldn't be needed.
Bye,
Oliver
Am 12.02.15 um 16:09 schrieb Mark Struberg:
ServiceLoader pattern.
beneficial use case I'm -1
[email protected]> wrote:
(?)
--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E [email protected]
S oliver.b.fischer
J [email protected]
X http://xing.to/obf
--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E [email protected]
S oliver.b.fischer
J [email protected]
X http://xing.to/obf
