You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Ted Husted <hu...@apache.org> on 2004/05/24 22:16:04 UTC
[Validator] Niall Pemberton as Committer
Niall Pemberton is an Apache Struts Committer who would like to apply some patches to the Validator, with the hope of moving toward another release.
Here's my +1
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Validator] Don Brown as Committer
Posted by Dirk Verbeeck <di...@pandora.be>.
+1
Ted Husted wrote:
> Don Brown is an active Apache Struts Committer who would like to apply some patches to the Validator, with the hope of moving toward another release.
>
> Here's my +1
>
> -Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Validator] Don Brown as Committer
Posted by Niall Pemberton <ni...@blueyonder.co.uk>.
Yes, these recently
http://issues.apache.org/bugzilla/show_bug.cgi?id=29205
http://issues.apache.org/bugzilla/show_bug.cgi?id=29151
http://issues.apache.org/bugzilla/show_bug.cgi?id=29145
----- Original Message -----
From: "Dion Gillard" <di...@gmail.com>
To: "Jakarta Commons Developers List" <co...@jakarta.apache.org>
Sent: Wednesday, May 26, 2004 2:35 AM
Subject: Re: [Validator] Don Brown as Committer
> Has Don submitted any patches for Validator yet?
>
> On Tue, 25 May 2004 12:18:59 -0400, Ted Husted <hu...@apache.org> wrote:
> >
> > Don Brown is an active Apache Struts Committer who would like to apply
some patches to the Validator, with the hope of moving toward another
release.
> >
> > Here's my +1
> >
> > -Ted.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Validator] Don Brown as Committer
Posted by Dion Gillard <di...@gmail.com>.
Has Don submitted any patches for Validator yet?
On Tue, 25 May 2004 12:18:59 -0400, Ted Husted <hu...@apache.org> wrote:
>
> Don Brown is an active Apache Struts Committer who would like to apply some patches to the Validator, with the hope of moving toward another release.
>
> Here's my +1
>
> -Ted.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
RE: [Validator] Don Brown as Committer
Posted by Matthias Wessendorf <ma...@matthias-wessendorf.de>.
read Don's mail about commons-validator
and his plans..., so here is my
+1
Cheers,
> -----Original Message-----
> From: Ted Husted [mailto:husted@apache.org]
> Sent: Tuesday, May 25, 2004 6:19 PM
> To: Jakarta Commons Developers List
> Subject: [Validator] Don Brown as Committer
>
>
> Don Brown is an active Apache Struts Committer who would like
> to apply some patches to the Validator, with the hope of
> moving toward another release.
>
> Here's my +1
>
> -Ted.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Validator] Don Brown as Committer
Posted by Robert Leland <rl...@apache.org>.
David Graham wrote:
>Don has been a positive member of the Struts community so he'll be a good
>addition to the validator team.
>
>+1
>
>
+1. And he has worked with other frameworks which a big +1
>David
>
>--- Ted Husted <hu...@apache.org> wrote:
>
>
>>Don Brown is an active Apache Struts Committer who would like to apply
>>some patches to the Validator, with the hope of moving toward another
>>release.
>>
>>Here's my +1
>>
>>-Ted.
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Validator] Don Brown as Committer
Posted by Martin Cooper <ma...@apache.org>.
On Tue, 25 May 2004, David Graham wrote:
> Don has been a positive member of the Struts community so he'll be a good
> addition to the validator team.
>
> +1
And mine: +1
--
Martin Cooper
> David
>
> --- Ted Husted <hu...@apache.org> wrote:
> > Don Brown is an active Apache Struts Committer who would like to apply
> > some patches to the Validator, with the hope of moving toward another
> > release.
> >
> > Here's my +1
> >
> > -Ted.
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Friends. Fun. Try the all-new Yahoo! Messenger.
> http://messenger.yahoo.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Validator] Don Brown as Committer
Posted by David Graham <gr...@yahoo.com>.
Don has been a positive member of the Struts community so he'll be a good
addition to the validator team.
+1
David
--- Ted Husted <hu...@apache.org> wrote:
> Don Brown is an active Apache Struts Committer who would like to apply
> some patches to the Validator, with the hope of moving toward another
> release.
>
> Here's my +1
>
> -Ted.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Validator] Ted Husted as Committer
Posted by David Graham <gr...@yahoo.com>.
--- Robert Leland <rl...@apache.org> wrote:
> +1 To Ted.
> David Graham wrote:
>
> >--- robert burrell donkin <ro...@blueyonder.co.uk> wrote:
> >
> >
> >>+1
> >>
> >>but please don't roll a release before the upcoming beanutils
> >>dependency hell fix is released. this will allow the problematic
> >>validator dependency on commons collections to be removed by upgrading
>
> >>to the next beanutils release.
> >>
> >>
> >
> >Actually, the removal of collections classes from validator will take a
> >bit longer.
> >
> Why is it that we want to remove FastHashMap ? is there a performance
> penalty ?
Its javadoc states that it's not cross platform. I have absolutely no
interest in using Java code that doesn't run on all platforms. Also,
that's our only usage of Commons Collections code so we can drop that
bulky dependency.
David
>
> Rob
>
> > We still have protected FastHashMap variables that need to be
> >replaced with Maps.
> >
> >David
> >
> >
>
>
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Validator] Ted Husted as Committer
Posted by Robert Leland <rl...@apache.org>.
+1 To Ted.
David Graham wrote:
>--- robert burrell donkin <ro...@blueyonder.co.uk> wrote:
>
>
>>+1
>>
>>but please don't roll a release before the upcoming beanutils
>>dependency hell fix is released. this will allow the problematic
>>validator dependency on commons collections to be removed by upgrading
>>to the next beanutils release.
>>
>>
>
>Actually, the removal of collections classes from validator will take a
>bit longer.
>
Why is it that we want to remove FastHashMap ? is there a performance
penalty ?
Rob
> We still have protected FastHashMap variables that need to be
>replaced with Maps.
>
>David
>
>
Re: [Validator] Collections dependencies
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
On 8 Jun 2004, at 09:06, Stephen Colebourne wrote:
>>> Actually, the removal of collections classes from validator will
>>> take a
>>> bit longer. We still have protected FastHashMap variables that need
>>> to be
>>> replaced with Maps.
>>
>> the collections packaged FashHashMap and it's dependencies are binary
>> compatible (in 2.x and 3.x collections - actually, they are identical)
>> and will be included as part of the next beanutils release.
>>
>> beanutils, validator and digester are in similar positions (and i
>> suspect from craig's comments earlier that struts is also) they need
>> the FastHashMap class (at least so that it can be deprecated) but they
>> don't need the other classes which have changed. so, those classes
>> they
>> need will be included as part of the beanutils distribution.
>>
>> therefore, it will be possible to remove the collections dependency by
>> upgrading to the upcoming beanutils. this will allow FastHashMap to be
>> repackaged or removed (as appropriate) in due course after
>> deprecation.
>
> I am +1 to the removal of the [collections] dependency here. However I
> must
> express caution at the implications of what seems to be described here.
>
> The idea appears to be that [validator] will obtain its copy of
> FastHashMap
> from [beanutils]. But this class will only be present in one release
> (1.7?)
> of [beanutils] and after that my understanding is that it will be
> removed.
> This would appear to be a very risky way of handling this, as you
> create a
> new dependency hell between [validator] and one specific release of
> [beanutils]. If I have understood correctly, I will -1 a valiator
> release
> :-(
>
> If the aim is to remove the [collections] depencency now, then
> FastHashMap
> should be copied (no package rename) to [validator] too. However,
> FastHashMap has not changed between [collections] 2.1 and 3.x, so
> perhaps
> removing the dependency is not urgent?
hmmm...
i suppose that it all depends on what is meant by dependencies. what's
important to avoid dependency hell is to ensure that one consistent set
of workable dependencies are chosen and applied consistently throughout
the environment.
having thought about this a little longer, it should be best for
validator (and struts) to be compiled against it's old dependencies
(just as you said). users then need only to ensure that they have the
right mix of compatible libraries throughout their classloaders.
for example, if a user wanted to use collections 3.x with new struts in
a web app in tomcat (with the option to use collection 2.x in others),
all that would be necessary would be to replace the collections 2.x and
older beanutils jars in the tomcat server library with the upcoming
beanutils release, remove the beanutils jar from the web-app library
and replace collections 2.x release with a collections 3.x release.
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Validator] Collections dependencies
Posted by David Graham <gr...@yahoo.com>.
--- Stephen Colebourne <sc...@btopenworld.com> wrote:
> > > Actually, the removal of collections classes from validator will
> take a
> > > bit longer. We still have protected FastHashMap variables that need
> > > to be
> > > replaced with Maps.
> >
> > the collections packaged FashHashMap and it's dependencies are binary
> > compatible (in 2.x and 3.x collections - actually, they are identical)
> > and will be included as part of the next beanutils release.
> >
> > beanutils, validator and digester are in similar positions (and i
> > suspect from craig's comments earlier that struts is also) they need
> > the FastHashMap class (at least so that it can be deprecated) but they
> > don't need the other classes which have changed. so, those classes
> they
> > need will be included as part of the beanutils distribution.
> >
> > therefore, it will be possible to remove the collections dependency by
> > upgrading to the upcoming beanutils. this will allow FastHashMap to be
> > repackaged or removed (as appropriate) in due course after
> deprecation.
>
> I am +1 to the removal of the [collections] dependency here. However I
> must
> express caution at the implications of what seems to be described here.
>
> The idea appears to be that [validator] will obtain its copy of
> FastHashMap
> from [beanutils]. But this class will only be present in one release
> (1.7?)
> of [beanutils] and after that my understanding is that it will be
> removed.
> This would appear to be a very risky way of handling this, as you create
> a
> new dependency hell between [validator] and one specific release of
> [beanutils]. If I have understood correctly, I will -1 a valiator
> release
> :-(
>
> If the aim is to remove the [collections] depencency now, then
> FastHashMap
> should be copied (no package rename) to [validator] too. However,
> FastHashMap has not changed between [collections] 2.1 and 3.x, so
> perhaps
> removing the dependency is not urgent?
We can deprecate the uses of FastHashMap in Validator for its upcoming
release and replace them with Map and HashMap references for the following
release. I'm against copying FastHashMap into Validator because that's a
stopgap measure for BeanUtils and Digester only.
David
>
> Stephen
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Validator] Collections dependencies
Posted by Stephen Colebourne <sc...@btopenworld.com>.
> > Actually, the removal of collections classes from validator will take a
> > bit longer. We still have protected FastHashMap variables that need
> > to be
> > replaced with Maps.
>
> the collections packaged FashHashMap and it's dependencies are binary
> compatible (in 2.x and 3.x collections - actually, they are identical)
> and will be included as part of the next beanutils release.
>
> beanutils, validator and digester are in similar positions (and i
> suspect from craig's comments earlier that struts is also) they need
> the FastHashMap class (at least so that it can be deprecated) but they
> don't need the other classes which have changed. so, those classes they
> need will be included as part of the beanutils distribution.
>
> therefore, it will be possible to remove the collections dependency by
> upgrading to the upcoming beanutils. this will allow FastHashMap to be
> repackaged or removed (as appropriate) in due course after deprecation.
I am +1 to the removal of the [collections] dependency here. However I must
express caution at the implications of what seems to be described here.
The idea appears to be that [validator] will obtain its copy of FastHashMap
from [beanutils]. But this class will only be present in one release (1.7?)
of [beanutils] and after that my understanding is that it will be removed.
This would appear to be a very risky way of handling this, as you create a
new dependency hell between [validator] and one specific release of
[beanutils]. If I have understood correctly, I will -1 a valiator release
:-(
If the aim is to remove the [collections] depencency now, then FastHashMap
should be copied (no package rename) to [validator] too. However,
FastHashMap has not changed between [collections] 2.1 and 3.x, so perhaps
removing the dependency is not urgent?
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Validator] Ted Husted as Committer
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
On 7 Jun 2004, at 04:22, David Graham wrote:
>
> --- robert burrell donkin <ro...@blueyonder.co.uk> wrote:
>> +1
>>
>> but please don't roll a release before the upcoming beanutils
>> dependency hell fix is released. this will allow the problematic
>> validator dependency on commons collections to be removed by upgrading
>> to the next beanutils release.
>
> Actually, the removal of collections classes from validator will take a
> bit longer. We still have protected FastHashMap variables that need
> to be
> replaced with Maps.
that will probably not be necessary :)
the collections packaged FashHashMap and it's dependencies are binary
compatible (in 2.x and 3.x collections - actually, they are identical)
and will be included as part of the next beanutils release.
beanutils, validator and digester are in similar positions (and i
suspect from craig's comments earlier that struts is also) they need
the FastHashMap class (at least so that it can be deprecated) but they
don't need the other classes which have changed. so, those classes they
need will be included as part of the beanutils distribution.
therefore, it will be possible to remove the collections dependency by
upgrading to the upcoming beanutils. this will allow FastHashMap to be
repackaged or removed (as appropriate) in due course after deprecation.
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Validator] Ted Husted as Committer
Posted by David Graham <gr...@yahoo.com>.
--- robert burrell donkin <ro...@blueyonder.co.uk> wrote:
> +1
>
> but please don't roll a release before the upcoming beanutils
> dependency hell fix is released. this will allow the problematic
> validator dependency on commons collections to be removed by upgrading
> to the next beanutils release.
Actually, the removal of collections classes from validator will take a
bit longer. We still have protected FastHashMap variables that need to be
replaced with Maps.
David
>
> - robert
>
> On 6 Jun 2004, at 13:39, Ted Husted wrote:
>
> > The few remaining issues against Validator seem to have fixes and
> > patches that I could apply. I'd like to resolve these issues and then
> > roll the 1.3.1 release.
> >
> > Accordingly, I'd like to nominate myself as a Validator Committer.
> >
> > Here's my +1 for me :)
> >
> > -Ted.
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Validator] Ted Husted as Committer
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
+1
but please don't roll a release before the upcoming beanutils
dependency hell fix is released. this will allow the problematic
validator dependency on commons collections to be removed by upgrading
to the next beanutils release.
- robert
On 6 Jun 2004, at 13:39, Ted Husted wrote:
> The few remaining issues against Validator seem to have fixes and
> patches that I could apply. I'd like to resolve these issues and then
> roll the 1.3.1 release.
>
> Accordingly, I'd like to nominate myself as a Validator Committer.
>
> Here's my +1 for me :)
>
> -Ted.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Validator] Ted Husted as Committer
Posted by Dion Gillard <di...@gmail.com>.
Aren't u already a commons committer? I thought we could just grant u karma...
On Sun, 6 Jun 2004 08:39:29 -0400, Ted Husted <hu...@apache.org> wrote:
>
> The few remaining issues against Validator seem to have fixes and patches that I could apply. I'd like to resolve these issues and then roll the 1.3.1 release.
>
> Accordingly, I'd like to nominate myself as a Validator Committer.
>
> Here's my +1 for me :)
>
> -Ted.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Validator] Ted Husted as Committer
Posted by James Mitchell <jm...@apache.org>.
+1 - Ted Husted for Validator Committer
+1 - Ted Husted for President
;)
--
James Mitchell
Software Engineer / Open Source Evangelist
EdgeTech, Inc.
678.910.8017
AIM: jmitchtx
----- Original Message -----
From: "Ted Husted" <hu...@apache.org>
To: "Jakarta Commons Developers List" <co...@jakarta.apache.org>
Sent: Sunday, June 06, 2004 8:39 AM
Subject: [Validator] Ted Husted as Committer
The few remaining issues against Validator seem to have fixes and patches
that I could apply. I'd like to resolve these issues and then roll the 1.3.1
release.
Accordingly, I'd like to nominate myself as a Validator Committer.
Here's my +1 for me :)
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Validator] Ted Husted as Committer
Posted by David Graham <gr...@yahoo.com>.
I thought you were already a Commons committer so I invited you to add
yourself to the project.xml file a while back. Regardless, here's my +1
:-).
David
--- Ted Husted <hu...@apache.org> wrote:
> The few remaining issues against Validator seem to have fixes and
> patches that I could apply. I'd like to resolve these issues and then
> roll the 1.3.1 release.
>
> Accordingly, I'd like to nominate myself as a Validator Committer.
>
> Here's my +1 for me :)
>
> -Ted.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Validator] Field class
Posted by David Graham <gr...@yahoo.com>.
I think this has been brought up before but nothing came of it. Feel free
to open a bugzilla enhancement ticket with patches and we'll apply them.
Thanks,
David
--- Rich Wertz <ra...@freerangedata.com> wrote:
> Recent validator DTDs indicate that each field element may have any
> number
> of child msg elements with optional attributes bundle and resource and
> required attributes key and name. Why then does the Field class not
> provide
> any accessor methods for retrieving Msg objects that have been
> associated
> with a particular field? The current getMsg() implementation returns
> only a
> String, even though an addMsg(Msg) method is provided. Shouldn't
> messages
> be handled by the Field class in a manner more consistent with its
> handling
> of Args?
>
> The primary use case needs driving these questions are 1) to be able to
> extract key, name, bundle, and resource y/n information for a particular
> message belonging to a field and, 2) to retrieve multiple messages from
> a
> particular field. I believe that this functionality would be
> particularly
> useful in situations where the validator is used as a standalone
> validation
> framework by applications, since it allows for more flexibility when
> analyzing ValidatorResult instances.
>
> Thanks!
>
> Rich
>
>
> -----Original Message-----
> From: Ted Husted [mailto:husted@apache.org]
> Sent: Sunday, June 06, 2004 7:39 AM
> To: Jakarta Commons Developers List
> Subject: [Validator] Ted Husted as Committer
>
> The few remaining issues against Validator seem to have fixes and
> patches
> that I could apply. I'd like to resolve these issues and then roll the
> 1.3.1
> release.
>
> Accordingly, I'd like to nominate myself as a Validator Committer.
>
> Here's my +1 for me :)
>
> -Ted.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[Validator] Field class
Posted by Rich Wertz <ra...@freerangedata.com>.
Recent validator DTDs indicate that each field element may have any number
of child msg elements with optional attributes bundle and resource and
required attributes key and name. Why then does the Field class not provide
any accessor methods for retrieving Msg objects that have been associated
with a particular field? The current getMsg() implementation returns only a
String, even though an addMsg(Msg) method is provided. Shouldn't messages
be handled by the Field class in a manner more consistent with its handling
of Args?
The primary use case needs driving these questions are 1) to be able to
extract key, name, bundle, and resource y/n information for a particular
message belonging to a field and, 2) to retrieve multiple messages from a
particular field. I believe that this functionality would be particularly
useful in situations where the validator is used as a standalone validation
framework by applications, since it allows for more flexibility when
analyzing ValidatorResult instances.
Thanks!
Rich
-----Original Message-----
From: Ted Husted [mailto:husted@apache.org]
Sent: Sunday, June 06, 2004 7:39 AM
To: Jakarta Commons Developers List
Subject: [Validator] Ted Husted as Committer
The few remaining issues against Validator seem to have fixes and patches
that I could apply. I'd like to resolve these issues and then roll the 1.3.1
release.
Accordingly, I'd like to nominate myself as a Validator Committer.
Here's my +1 for me :)
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
RE: [Validator] Ted Husted as Committer
Posted by Martin Cooper <ma...@apache.org>.
Hey Ted,
You already have Commons karma, so all you need to do is add yourself to the
status file (and project.xml, I guess) and have at it. +1 from me anyway.
;-)
--
Martin Cooper
> -----Original Message-----
> From: Ted Husted [mailto:husted@apache.org]
> Sent: Sunday, June 06, 2004 5:39 AM
> To: Jakarta Commons Developers List
> Subject: [Validator] Ted Husted as Committer
>
>
> The few remaining issues against Validator seem to have fixes and
> patches that I could apply. I'd like to resolve these issues and
> then roll the 1.3.1 release.
>
> Accordingly, I'd like to nominate myself as a Validator Committer.
>
> Here's my +1 for me :)
>
> -Ted.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[Validator] Ted Husted as Committer
Posted by Ted Husted <hu...@apache.org>.
The few remaining issues against Validator seem to have fixes and patches that I could apply. I'd like to resolve these issues and then roll the 1.3.1 release.
Accordingly, I'd like to nominate myself as a Validator Committer.
Here's my +1 for me :)
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[Validator] Don Brown as Committer
Posted by Ted Husted <hu...@apache.org>.
Don Brown is an active Apache Struts Committer who would like to apply some patches to the Validator, with the hope of moving toward another release.
Here's my +1
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Validator] Niall Pemberton as Committer
Posted by Martin Cooper <ma...@apache.org>.
On Mon, 24 May 2004, Ted Husted wrote:
> Niall Pemberton is an Apache Struts Committer who would like to apply some patches to the Validator, with the hope of moving toward another release.
>
> Here's my +1
And mine: +1
--
Martin Cooper
>
> -Ted.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Validator] Niall Pemberton as Committer
Posted by Robert Leland <rl...@apache.org>.
Ted Husted wrote:
>Niall Pemberton is an Apache Struts Committer who would like to apply some patches to the Validator, with the hope of moving toward another release.
>
>Here's my +1
>
>
+1, yes I am a bit behind on my email. :-} !
>-Ted.
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Validator] Niall Pemberton as Committer
Posted by Dirk Verbeeck <di...@pandora.be>.
+1
Ted Husted wrote:
> Niall Pemberton is an Apache Struts Committer who would like to apply some patches to the Validator, with the hope of moving toward another release.
>
> Here's my +1
>
> -Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Validator] Niall Pemberton as Committer
Posted by James Mitchell <jm...@apache.org>.
+1
--
James Mitchell
Software Engineer / Open Source Evangelist
EdgeTech, Inc.
678.910.8017
AIM: jmitchtx
----- Original Message -----
From: "Ted Husted" <hu...@apache.org>
To: "Jakarta Commons Developers List" <co...@jakarta.apache.org>
Sent: Monday, May 24, 2004 4:16 PM
Subject: [Validator] Niall Pemberton as Committer
Niall Pemberton is an Apache Struts Committer who would like to apply some
patches to the Validator, with the hope of moving toward another release.
Here's my +1
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Validator] Niall Pemberton as Committer
Posted by Dion Gillard <di...@gmail.com>.
+1
On Mon, 24 May 2004 16:16:04 -0400, Ted Husted <hu...@apache.org> wrote:
>
> Niall Pemberton is an Apache Struts Committer who would like to apply some patches to the Validator, with the hope of moving toward another release.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Validator] Niall Pemberton as Committer
Posted by Henri Yandell <ba...@generationjava.com>.
Sounds like a fine idea.
+1
On Mon, 24 May 2004, Ted Husted wrote:
> Niall Pemberton is an Apache Struts Committer who would like to apply some patches to the Validator, with the hope of moving toward another release.
>
> Here's my +1
>
> -Ted.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Validator] Niall Pemberton as Committer
Posted by David Graham <gr...@yahoo.com>.
Niall's been a positive contributing member in the Struts community and I
see no reason he wouldn't be in Validator as well. In addition, Validator
could use a few more active committers.
+1
David
--- Ted Husted <hu...@apache.org> wrote:
> Niall Pemberton is an Apache Struts Committer who would like to apply
> some patches to the Validator, with the hope of moving toward another
> release.
>
> Here's my +1
>
> -Ted.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
RE: [Validator] Niall Pemberton as Committer
Posted by Matthias Wessendorf <ma...@matthias-wessendorf.de>.
+1
> -----Original Message-----
> From: Ted Husted [mailto:husted@apache.org]
> Sent: Monday, May 24, 2004 10:16 PM
> To: Jakarta Commons Developers List
> Subject: [Validator] Niall Pemberton as Committer
>
>
> Niall Pemberton is an Apache Struts Committer who would like
> to apply some patches to the Validator, with the hope of
> moving toward another release.
>
> Here's my +1
>
> -Ted.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org