+1 for the URL, IMO no need of any more abstraction here for now. If you need a "locator" then json property source is broken since it is already the format so it only needs the input stream - URL is a nice way to abstract it and easy to get from File, classloader, http...
Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2015-01-06 8:29 GMT+01:00 Oliver B. Fischer <[email protected]>: > Dear all, > > we have to clarify how do we find a property source at the end of the day. I > have seen now three different apporaches: > > 1. org.apache.tamaya.format.ConfigurationFormat interface by Anatole > 2. Using an URL by Reinhard > 3. Custom interface by me for the JSON PropertySource > > The solution by Anatole and me is very similar and could be unified easily. > Independent of the way we go this interface belongs to the core module. Or > not? > > Furthermore how does a normal Java SE user will use it? How does the top > level usage of Tamaya looks like? > > 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 >
