In the case where the calls to TraversableResolver methods are fast, caching them is not a good idea. So the user should be able to disable this cache.

Another point is that TraversableResolver initialization is currently a bit of a mess: the default one is in fact a wrapper around a potential JPA specific one. And it might be wrapped again into a CachingTraversableResolverForSingleValidation.

We could get rid of this wrapping layer and have a TraverseAllTraversingResolver and the JPA one and create one or the other depending on what's required.