Hi, This is already the case because all resource providers on a certain level are ordered according to their ServiceReference.compareTo. Thus the service.ranking and service.id are considered for the ordering.
Regards Felix On 24.08.2010 17:52, Carsten Ziegeler wrote: > Mike Müller wrote >> Hi >> >> That seems to be a good way to implement it. IIRC the resource providers >> are called in order starting with the provider which is registered >> for the longest part of the requested path. If that is correct the >> SyntheticResourceProvider (which I rather would name something like >> PathNodeProvider) should be registered for "/", where also the >> JcrResourceProvider is registered. The question is now, how the >> resource provider which are registered for the same path could be >> further ordered (the service id doesn't seem to be a good idea). >> Any idea? >> > We could use service.ranking property - the standard way of defining an > order in such cases. > > Carsten
