You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bval.apache.org by "Romain Manni-Bucau (JIRA)" <ji...@apache.org> on 2016/09/27 13:43:20 UTC
[jira] [Updated] (BVAL-147) TraversableResolver,
ConstraintValidatorFactory and MessageInterpolator shouldnt invalidate the
metadata cache
[ https://issues.apache.org/jira/browse/BVAL-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Romain Manni-Bucau updated BVAL-147:
------------------------------------
Description:
We can reuse the shared cache of metadata even with a custom TraversableResolver, constraint factory or interpolator since it only affects runtime and not static data
This leads to a huge perf boost with hibernate as JPA provider
was:
We can reuse the shared cache of metadata even with a custom TraversableResolver since it only affects runtime and not static data
This leads to a huge perf boost with hibernate as JPA provider
> TraversableResolver, ConstraintValidatorFactory and MessageInterpolator shouldnt invalidate the metadata cache
> --------------------------------------------------------------------------------------------------------------
>
> Key: BVAL-147
> URL: https://issues.apache.org/jira/browse/BVAL-147
> Project: BVal
> Issue Type: Bug
> Reporter: Romain Manni-Bucau
> Assignee: Romain Manni-Bucau
> Fix For: 1.1.2
>
>
> We can reuse the shared cache of metadata even with a custom TraversableResolver, constraint factory or interpolator since it only affects runtime and not static data
> This leads to a huge perf boost with hibernate as JPA provider
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)