In the case where
Currently 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:
- we have the default one which is in fact a wrapper itself around a potential JPA specific one
- we wrap this with . And it might be wrapped again into a {{CachingTraversableResolverForSingleValidation}} .
In the simple case where we just want We could get rid of this wrapping layer and have a "traverse all" {{ TraversableResolver TraverseAllTraversingResolver }} , we should avoid all this wrapping, especially and the caching JPA one as it has some serious cost and create one or the other depending on what's required . |
|
