CapeDwarf had a use case. ...

Are you not putting the cart before the horse? You are saying an app class loader which does not see Search and CapeDwarf depending on Search, etc. Is the question not what gets passed to Search? I would love, if you could explain your example in more detail, so that I also understand the need to provide more than one extra class loader to Search. I am not against it and in fact the aggregated class loader in ORM can have an arbitrary list of class loaders, but I am still wondering about how exactly the more than one extra classloader case looks like.