Hi, right now, the only possible way to get the configured search paths for resource resolving is to actually create a resource resolver (by logging in using a service user). Then the search paths array can be get from the resolver and the resolver can be closed. This is pretty expensive for just getting a setting.
In theory, each resolver could have different search paths; in reality we never went down this road and I think in fact we can't. There is a lot of code out there, assuming that each resolver has the same search paths; the resource change listener act in exactly the same way. Therefore I suggest we simply add the search paths as a service registration property of the resource resolver factory. This makes getting this setting very easy without even getting a service. WDYT? Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland [email protected]
