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 (nike.apache.org: domain of niall.pemberton@gmail.com
 designates 209.85.211.174 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=qM098J4VvB+ak5T5DOHeagn7TJxTcpQeNwtKHYhNviW/zws1RTPJBDr2NYl2I1MMqe
         7maYy1cwbr33hAqgSuJ4zCyAFoM9DteWZ/kNxn90bOCeTa1lCiBzZlvXtu3nTacI4yYA
         rx8CVU45Qlckf6s6IHUuiCReK5cNR6qElX4B0=
MIME-Version: 1.0
Date: Fri, 23 Oct 2009 03:33:34 +0100
Message-ID: <55afdc850910221933y2e6d8a12ncafb9dfb247e0922@mail.gmail.com>
Subject: [validator] Direction of validator implementation based on JSR 303
From: Niall Pemberton <niall.pemberton@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

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:

  - The Bean Validation (JSR303) API - no dependencies
  - Standalone Validation Routines (based on existing validator
routines package) - no dependencies including Bean Validation API
  - 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/alternative/

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/alternative/validation-api/
[2] http://svn.apache.org/viewvc/commons/sandbox/validator2/branches/alternative/validation-routines/
[3] http://svn.apache.org/viewvc/commons/sandbox/validator2/branches/alternative/validation-framework/

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