The point is API is not done to have auto reading of resources cause it makes no sense in most of cases: xml, json, yaml, txt...all these formats need more than knowing the extension to be able to read it. It means PropertySource has to link path and format which is the role of the provider you have to write.
Said otherwise each kind of file type you ll discover will need its provider otherwise if you do what you described you ll just manage to not get the expected conf (in the best case) Le 13 févr. 2015 00:09, "Oliver B. Fischer" <[email protected]> a écrit : > It helps me to locate resources, right? But if I understand it correctly > it helps me to get a bunch of URLs. So I am at the same point as before. > > Bye, > > Oliver > > > > Am 12.02.15 um 20:51 schrieb Anatole Tresch: > >> Look at the resources extension. It supports Spring styled path resolution >> to a collection of URLs. Will work in SE, Weblogic, and basically should >> also in JBoss/Wildfly, but must be tested there since the guys have some >> interesting classloader design there, which must be handled differently... >> Basically the extension register another service called ResourceResolver >> to >> the ServiceContext.... so we are back to my second original proposal using >> formats as well ;) >> >> 2015-02-12 20:40 GMT+01:00 Oliver B. Fischer <[email protected]>: >> >> Hi Antole, my problem is simply that I dont know which PropertySources do >>> exist. There might be 0 to x possible PropertySources available in the >>> classpath. So the question is how to I detect them and the method I have >>> to >>> call with the given URL. >>> >>> Von meinem iPhone gesendet >>> >>> this >>> simple >>> maps >>> 2015 >>> PropertySourceLocator >>> to >>> one >>> BTW >>> not >>> to >>> be >>> to >>> location, >>> may >>> >> >> >> > -- > 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 > >
