Each particular implementation of this interface may define its own mechanism for searching for resources. Please see the documents for each particular implementation to determine its behavior and to see how it can be configured.
It is important to note that if a resource is not found by a particular loader than the loader should return null rather than throw an exception. The reason for this is that loaders can be arranged in a chain and it would be very inefficient for loaders earlier in the chain to throw exceptions that must be caught and handled each time until the correct loader in the chain is reached.
@see org.apache.wicket.settings.IResourceSettings
@author Chris Turner
@author Juergen Donnerstag
| |