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:
Furthermore we said the origin of a
source must be overhanded as a URL (file://somewhere/).
Nope. You pass in a PropertySource programmatically or register it via
ServiceLoader pattern.
That is fine and works. But IMHO we miss the connection between them.
How to specify a specific property source and to find the matching
PropertySource?
You should not need to do this.
WDYT?
Give me the use case and I gonna think about it. Without a really beneficial
use case I'm -1
LieGrue,
strub
On Thursday, 12 February 2015, 8:25, Oliver B. Fischer
<[email protected]> wrote:
Dear all,
PropertySource is our abstraction for different property sources and
formats. I think we agree on this. Furthermore we said the origin of a
source must be overhanded as a URL (file://somewhere/).
That is fine and works. But IMHO we miss the connection between them.
How to specify a specific property source and to find the matching
PropertySource?
Therefore I would like to propose a option SPI: PropertySourceLocator (?)
PropertySourceLocator#accepts(URL url):boolean
PropertySourceLocator#get(URL url): PropertySource
WDYT?
Oliver
--
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
