Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of niall.pemberton@gmail.com
 designates 72.14.214.237 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=WEfynMj7gAGXu+Lc9jeEzDqHKvw0lWUdbSWfJWCxEmsij1GBLOmq9ZYW1Qr3d1yDud+Ou8C2G6asZijxxKcUz+Y14zM8fAGz9zq3dLjes2hHtfrV+f3+vjbTb1+DtWK/VdeUuQxCL/Z9MNp+7CdD7OAPVCVL0CLlM2Nehsjutd0=
Message-ID: <55afdc850803260809v6ab52339o8eedf8256bccf8cc@mail.gmail.com>
Date: Wed, 26 Mar 2008 15:09:43 +0000
From: "Niall Pemberton" <niall.pemberton@gmail.com>
To: "Jakarta Commons Developers List" <dev@commons.apache.org>
Subject: Re: [Validator] Apache Commons Validator and JSR#303
In-Reply-To: <f321b69f0803260802v5914fdb7rb36786092155738c@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <f321b69f0803260706s4c335cnb3e4e85a14e26705@mail.gmail.com>
	 <55afdc850803260749y275ccee9pb64d00d1e62ad91d@mail.gmail.com>
	 <f321b69f0803260754w72aa671fg4fc681f3576117f5@mail.gmail.com>
	 <f321b69f0803260757s61dae514yf1a531ada54444fb@mail.gmail.com>
	 <55afdc850803260758q750ea6c9p4779f4cb618c593@mail.gmail.com>
	 <f321b69f0803260802v5914fdb7rb36786092155738c@mail.gmail.com>

On Wed, Mar 26, 2008 at 3:02 PM, Mohammad Nour El-Din
<nour.mohammad@gmail.com> wrote:
> Sorry for the last stupid question I could have know it from site, but
>  one more - I hope not stupid - question, you will apply the Validator2
>  code in trunk and make old validator in a separate branch ???

>From memory, the trunk is nearly ready for a release - I kind of
answered this in another mail, but probably initially in a branch or
perhaps the Sandbox.

Niall


>  On Wed, Mar 26, 2008 at 4:58 PM, Niall Pemberton
>
>
> <niall.pemberton@gmail.com> wrote:
>  > On Wed, Mar 26, 2008 at 2:57 PM, Mohammad Nour El-Din
>  >
>  > <nour.mohammad@gmail.com> wrote:
>  >
>  > > Just to make sure, this is where trunk code exist
>  >  >
>  >  >  http://svn.apache.org/repos/asf/commons/proper/validator/trunk/
>  >  >
>  >
>  >  Yes
>  >
>  >  Niall
>  >
>  >
>  >
>  >  >
>  >  >  On Wed, Mar 26, 2008 at 4:54 PM, Mohammad Nour El-Din
>  >  >
>  >  > <nour.mohammad@gmail.com> wrote:
>  >  >
>  >  >
>  >  > > I skimmed over the JSR - not a detailed look actually - and through
>  >  >  >  using annotations you declare the validator class, so we can adapt the
>  >  >  >  current validators, or at least make minor changes to make them
>  >  >  >  suitable to be used through JSR#303/Validator2 impl. I will download
>  >  >  >  the code today and take a more detailed look at JSR PDF and if I found
>  >  >  >  more info I will send them back by the end of this week.
>  >  >  >
>  >  >  >
>  >  >  >
>  >  >  >  On Wed, Mar 26, 2008 at 4:49 PM, Niall Pemberton
>  >  >  >  <niall.pemberton@gmail.com> wrote:
>  >  >  >  >
>  >  >  >  > On Wed, Mar 26, 2008 at 2:06 PM, Mohammad Nour El-Din <mnour@apache.org> wrote:
>  >  >  >  >  > Hi All...
>  >  >  >  >  >
>  >  >  >  >  >   Recently an EDR JSR#303 has been published on JCP -
>  >  >  >  >  >  http://jcp.org/en/jsr/detail?id=303 . They intend to make a unified
>  >  >  >  >  >  Bean Validation APIs/Framework based on using annotations and XML
>  >  >  >  >  >  configuration files, and they define the way how to apply and use
>  >  >  >  >  >  validation, and it will be part of the Java Beans model.
>  >  >  >  >  >
>  >  >  >  >  >  I am a committer in Apache OpenEJB, and we need such functionality for
>  >  >  >  >  >  bean validation through the process of deploying an enterprise java
>  >  >  >  >  >  bean - we have a home made validation framework now. And I have a
>  >  >  >  >  >  colleague of mine who is working in Apache MyFaces Tomahawk-
>  >  >  >  >  >  http://myfaces.apache.org/tomahawk/index.html - and he is interested
>  >  >  >  >  >  in such functionality to apply validation regarding JSF.
>  >  >  >  >  >
>  >  >  >  >  >  My colleague and I are very interested in implementing this JSR in
>  >  >  >  >  >  Apache Commons Validator, but seems that the project is not active for
>  >  >  >  >  >  a while, so I am asking how our changes are going to be applied to
>  >  >  >  >  >  Commons Validator. I mean are we going to submit changes in patches
>  >  >  >  >  >  and someone will review and commit - but no one is active now to do
>  >  >  >  >  >  that. Or I can get a committer access to apply changes and review
>  >  >  >  >  >  patches submitted by my colleague. Please advice and help.
>  >  >  >  >
>  >  >  >  >  Do you have an idea how you want to do this in Commons Validator?
>  >  >  >  >  Specifically I'm wondering whether this would be a re-write or whether
>  >  >  >  >  you think the exisiting framework could be adapated to JSR 303? My
>  >  >  >  >  thinking was that implementing JSR 303 would involved and
>  >  >  >  >  brand-new-replacement for the existing framework - Validator2.
>  >  >  >  >
>  >  >  >  >  Niall
>  >  >  >  >
>  >  >  >  >
>  >  >  >  >  >  P.S. I need your reply ASAP to stat planning and coordination with my colleague.
>  >  >  >  >
>  >  >  >  >
>  >  >  >  >
>  >  >  >  > ---------------------------------------------------------------------
>  >  >  >  >  To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>  >  >  >  >  For additional commands, e-mail: dev-help@commons.apache.org
>  >  >  >  >
>  >  >  >  >
>  >  >  >
>  >  >  >
>  >  >  >
>  >  >  >  --
>  >  >  >  Thanks
>  >  >  >  - Mohammad Nour
>  >  >  >
>  >  >
>  >  >
>  >  >
>  >  >  --
>  >  >  Thanks
>  >  >  - Mohammad Nour
>  >  >
>  >  >  ---------------------------------------------------------------------
>  >  >  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
>  >
>  >
>
>
>
>  --
>  Thanks
>  - Mohammad Nour
>
>  ---------------------------------------------------------------------
>  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