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/02/03 09:26:39 UTC

[jira] [Updated] (BVAL-143) meta cache not shared accross validator instances

     [ https://issues.apache.org/jira/browse/BVAL-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Romain Manni-Bucau updated BVAL-143:
------------------------------------
    Fix Version/s:     (was: 1.1.0)
                   1.1.0-alpha2

> meta cache not shared accross validator instances
> -------------------------------------------------
>
>                 Key: BVAL-143
>                 URL: https://issues.apache.org/jira/browse/BVAL-143
>             Project: BVal
>          Issue Type: Bug
>            Reporter: Romain Manni-Bucau
>            Assignee: Romain Manni-Bucau
>             Fix For: 1.1.0-alpha2
>
>
> we cache metadata and it works fine while you reuse the same Validator instance (case in TomEE for instance) but if user is relying himself on the ValidatorFactory and gets a Validator for each request it is super slow since the model is rebuilt each time.
> We should at least ensure if the ValidatorContext is not customized we don't recompute metadata - another jira could cache in the factory depending the context customization but it is more hazardous so this jira is just about making the default good (ie if context is not customized we dont recompute metadata).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)