Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of paulus.benedictus@gmail.com
 designates 209.85.210.189 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=bvIcuO1vMmwAWf0MRl4QvuicfOMmuTRbT17JWpX5GIeORuC+ZN7i5lOnlo8mn3yXBZ
         LIPsa6XKcBJQnKGmWlqfbxcfzwGu7CXirnlootVBb3zAHRNUMVp/D+VaiKSrtO2/VxgI
         ZXOPKpzNV3SceJGUvLcGM39pw2K6b+4VAUmZk=
MIME-Version: 1.0
Sender: paulus.benedictus@gmail.com
In-Reply-To: <55afdc850910221933y2e6d8a12ncafb9dfb247e0922@mail.gmail.com>
References: <55afdc850910221933y2e6d8a12ncafb9dfb247e0922@mail.gmail.com>
Date: Fri, 23 Oct 2009 01:17:53 -0500
Message-ID: <b9e663070910222317i748d9508ge658c91b19cc4d0a@mail.gmail.com>
Subject: Re: [validator] Direction of validator implementation based on JSR
	303
From: Paul Benedict <pbenedict@apache.org>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

+1

On Thu, Oct 22, 2009 at 9:33 PM, Niall Pemberton
<niall.pemberton@gmail.com> wrote:
> The current trunk in the validator2 sandbox is a copy of the Validator
> 1.4 code from "commons proper" - but I think we should dump all the
> existing validator framework code and just retain the "routines"
> package. Trying to maintain any sort of compatibility with the
> existing validator framework would be alot more work and code and
> create a real mess IMO and I think it would be better to not to even
> try. The "routines" package was refactored realtively recently(!) and
> can stand on its own.
>
> So I would like to propose the following direction for a Validator2
> based on the Bean Validation Framework(JSR 303) - a project with three
> separate modules composing of:
>
> =A0- The Bean Validation (JSR303) API - no dependencies
> =A0- Standalone Validation Routines (based on existing validator
> routines package) - no dependencies including Bean Validation API
> =A0- Validation Framework - JSR303 implementation (depends on two modules=
 above)
>
> I have created an alternative branch in the Validator sandbox project
> based on the above approach:
>
> http://svn.apache.org/viewvc/commons/sandbox/validator2/branches/alternat=
ive/
>
> I have created a "clean room" implementation of the Bean Validation
> API[1] which (hopefully) is complete except for JavaDocs. The only
> real functionality is in javax.validation.Validation - the rest are
> annotations, interfaces and exceptions. I have also copied the
> "routines" package into a standalone module[2]. So the next thing is
> to start the actual framework implementation module.
>
> How does this sound as an approach?
>
> Niall
>
> [1] http://svn.apache.org/viewvc/commons/sandbox/validator2/branches/alte=
rnative/validation-api/
> [2] http://svn.apache.org/viewvc/commons/sandbox/validator2/branches/alte=
rnative/validation-routines/
> [3] http://svn.apache.org/viewvc/commons/sandbox/validator2/branches/alte=
rnative/validation-framework/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org