Mailing-List: contact dev-help@click.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@click.apache.org
Date: Sat, 2 Nov 2013 15:18:18 +0000 (UTC)
From: "Adrian A. (JIRA)" <jira@apache.org>
To: dev@click.apache.org
Message-ID: <JIRA.12467402.1276957307081.10861.1383405498707@arcas>
In-Reply-To: <JIRA.12467402.1276957307081@arcas>
References: <JIRA.12467402.1276957307081@arcas>
Subject: [jira] [Updated] (CLK-698) Hibernate Validator Support
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Adrian A. updated CLK-698:
--------------------------

    Fix Version/s: 3.0.0

> Hibernate Validator Support
> ---------------------------
>
>                 Key: CLK-698
>                 URL: https://issues.apache.org/jira/browse/CLK-698
>             Project: Click
>          Issue Type: New Feature
>          Components: examples
>            Reporter: George Stan
>             Fix For: 3.0.0
>
>
> Click has very nice and smart validation in each component, and they're also in the right place - in the View.
> Projects using Hibernate, tend to put the validation rules in the Model, using Hibernate-Validator (even if this
> is not the best strategy considering that there are more views with different validation rules that act on the same
> model - e.g. and Admin View would have different rules than the more restricted User View).
> It would be really helpful and time saving if the Hibernate-Click integration would also support Hibernate-Validator, to automatically
> generate Click validations out of Hibernate validation rules present in the model as annotations.


--
This message was sent by Atlassian JIRA
(v6.1#6144)