ResourceObjectProviderBase should have custom exception to distinguish between different kinds of failures

[reckart]

Currently, configure() from ResourceObjtectProviderBase throws only a IOException()...
it should throw more fine-grained exceptions, e.g. because a mapping was not found,
because a resource was not found, because a resource JAR could not be resolved, etc...

Original issue reported on code.google.com by pedrobssantos on 2014-09-09 15:35:21