org.mule.api.registry

Interface ServiceRegistry

All Known Implementing Classes:

SpiServiceRegistry

public interface ServiceRegistry

Locates and returns all registered instances of a given provider class. Advantages of using this interface instead of hitting something like ServiceLoader directly are the ability to inject a different lookup mechanism and to facilitate testing.

Since:

3.7.0

Method Summary

Methods

Modifier and Type	Method and Description
<T> Collection<T>	lookupProviders(Class<T> providerClass) Searches for implementations of a particular service class
<T> Collection<T>	lookupProviders(Class<T> providerClass, ClassLoader loader) Searches for implementations of a particular service class using the given class loader.

Method Detail

lookupProviders

<T> Collection<T> lookupProviders(Class<T> providerClass,
                                ClassLoader loader)

Searches for implementations of a particular service class using the given class loader.

Parameters:

providerClass - a Classobject indicating the class or interface of the service providers being detected.

loader - the class loader to be used to load provider/configuration files and instantiate provider instances. If null, it will be up to the implementation to choose a ClassLoader

Returns:

A Collection that yields provider objects for the given service, in some arbitrary order.

lookupProviders

<T> Collection<T> lookupProviders(Class<T> providerClass)

Searches for implementations of a particular service class

Parameters:

providerClass - a Classobject indicating the class or interface of the service providers being detected.

Returns:

A Collection that yields provider objects for the given service, in some arbitrary order.