Re: [validator] UrlValidator

> Question 3) > Changing the UrlValidator should be a matter of getting the regular > expression correct I believe(?) for the empty path parts. > One thought I had on port validation was to attempt to construct a > java.net.URL and do something like 2 problems with thatg: 1 ) I believe there is no

Re: [Validator] Ted Husted as Committer

+1 To Ted. David Graham wrote: --- robert burrell donkin <[EMAIL PROTECTED]> 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 n

Re: [Validator] Niall Pemberton as Committer

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. -

Re: [validator] Why doesn't commons-validator include functional validators?

We wanted add a standard isValid() type method a years ago, but there was not clear use case for that. Now we have the use cases ! Don Brown wrote: Just to be clear, the approach I feel would be simplest is to add "isValid(Object bean, Field field)"-type methods to each validator. This way, the

Re: [Validator] Don Brown as Committer

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 <[EMAIL PROTECTED]> wrote: Don Brown is an active Apache Struts Committer who would

Re: [validator] Schematron-type/XPath Validator

Don Brown wrote: I have seen how powerful JXPath can be in projects like PMD Just to be cautious maybe we could place the code initially in a contrib folder, to take a look at it ? I wrote a simple Validator that uses JXPath to implement a schematron-style validation where fields are evaluated

Re: [beanutils] PROPOSAL: eliminate core dependency on collections

> -Original Message- > From: robert burrell donkin [mailto:[EMAIL PROTECTED]> > PROPOSAL: eliminate the core dependency on commons-collections > > rationale - this will not only eliminate a sizable dependency for many > products depending on beanutils but also reduce chances of > compatib

Re: [Validator] 1.1.3 Release

ks fine with > nightly builds from struts > > thanks! > > > -Original Message- > > From: Robert Leland [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, April 27, 2004 10:20 PM > > To: Jakarta Commons Developers List > > Subject: Re: [Validator] 1.1.3

Re: [Validator] 1.1.3 Release

+1, Thanks If anyone would like to try out that release before hand the can go to http://apache.org/~rleland/commons-validator I uploaded it based on a build from the 1_1_2_BRANCH last night. -Rob > -Original Message- > From: Ted Husted [mailto:[EMAIL PROTECTED] > Sent: Tuesda

Re: cvs commit: jakarta-commons/validator/src/share/org/apache/commons/validator ValidatorAction.java

No problem, you're focusing on the 1.2.0. I am trying to keep the 1.1.3 branch upto date so when the next RM is ready to cut it will be ready to go. -Rob > -Original Message- > From: David Graham [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 13, 2004 12:53 PM > To: 'Jakarta Commons De

[Validator] call for testers.

I would like to entice developers to give the Struts Nightly and/or the commons-validator a try. I am announcing this only on the 'dev' list in the belief that since you subscribed to the 'dev' list you are generally more advanced. Also since I will be in a crunch for the next few days I can't pr

Re: [Validator] Url Validation Patch - [Bug 28190]

Robert Leland wrote: Niall Pemberton wrote: Any feedback on the patch I submitted adding the ability to return an error code from when validating Url's? http://issues.apache.org/bugzilla/show_bug.cgi?id=28190 Niall I have a deadline this Friday that will probably stretch ove

Re: [Validator] Url Validation Patch - [Bug 28190]

Niall Pemberton wrote: Any feedback on the patch I submitted adding the ability to return an error code from when validating Url's? http://issues.apache.org/bugzilla/show_bug.cgi?id=28190 Niall I have a deadline this Friday that will probably stretch over the weekend. After that I'll have a

Re: [betwixt] extensible optional parameters in .betwixt file

> my proposed name for the tag is 'option' (since property could be how about 'behavior' ? -Rob - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: [validator] 1.1.2 build issues

> -Original Message- > From: David Graham [mailto:[EMAIL PROTECTED]> > What do we want to do with validator_1_1_2.dtd? I think we can remove it > completely because, AFAICT, Rob removed the only new changes so it's now > functionally equivalent to the 1.1 dtd. +1 > > David > Rob

Re: [VOTE] [Validator] Validator 1.1.2 release

Martin Cooper wrote: > > >--- >Vote: Commons Validator 1.1.2 Release >[X] +1 I am in favor of the release, and will help support it >[ ] +0 I am in favor of the release, but am unable to help support it >[ ] -0 I am not in favor o

[Validator] release(was : Re: Counting down to the 1.2.1 release)

Martin Cooper wrote: >There have been some Validator discussions going on on commons-dev, >related to JavaScript, so I'm going to wait for a green light from someone >(David G?) before I roll Validator 1.1.2. Ok, Validator is now using DOM Level 1 compatable calls to resolve the form name. Thank

[Vote][Result] Release of Commons Validator 1.1.1

up.com/?l=jakarta-commons-dev&m=107154253909393&w=4>, the result was: 5 +1 votes, (If you count my Implied +1 vote) 0 0 votes 0 -1 votes. So it is again available for download at http://jakarta.apache.org/~rleland/ValidatorAlpha/1.1.1 -Rob Robert Leland wrote: For the moment I have w

Re: [Vote] Release of Commons Validator 1.1.1

Noel J. Bergman wrote: Vote: Commons Validator 1.1.1 Release [ ] +1 I am in favor of the release, and will help support it [X] +0 I am in favor of the release, but am unable to help support it [ ] -0 I am not in favor of the release [ ] -1 I am against this proposal (must include a reason). Quest

[Vote] Release of Commons Validator 1.1.1

For the moment I have withdrawn commons-validator, and we'll take a vote on its release, see bottom. The following release plan is proposed for Validator 1.1.0: * /Tag Date/ - Tuesday, December 15, 2003, 02:00:00 EST * /Release Manager/ - Robert Leland * /Alpha Release Announcement/

[ANNOUNCE] Commons-Validator 1.1.1 released

Commons Validator 1.1.1 is now available for testing. Please refer to http://jakarta.apache.org/commons/validator/tasks.html that details the changes that have taken place since the 1.1.0 release. Downloads: http://jakarta.apache.org/~rleland/ValidatorAlpha/1.1.1 Just a reminder : The release proc

Re: [validator] API docs missing from site

Phil Steitz wrote: The links to both the "legacy 1.0.2" and current (maven report) javadocs are currently broken on the validator site. Looks like the API docs have been moved or deleted. Phile, Fixed, Thanks ! - To unsubscrib

Re: Company Acknowledgements [was :Re: [HiveMind] 1.0 Beta]

[EMAIL PROTECTED] wrote: Robert Leland <[EMAIL PROTECTED]> wrote on 05/11/2003 01:52:48 PM: [snip] (Maven has some hidden acknowledgments in it's plug-in docs) says you I saw them back in September at the very bottom of page the PMD plugin docs: http://maven.apache.or

Re: [validator] EmailTest failing

Peter Courcoux wrote: Hi all, I did a fresh checkout of validator this evening and the EmailTest failed. Your correct, those tests were added as a reminder to review the RFC822.txt and handle cases of specialized characters in the users name. Most of the time the character string needs to be

Re: Company Acknowledgements [was :Re: [HiveMind] 1.0 Beta]

Howard M. Lewis Ship wrote: So, what would you propose? Strip HiveMind out of the sandbox CVS? Track down any backup mirrors and erase them? Kidnap its users and brain wash them? You've acknowledged that when you commit any code to Apache you give up ownership of that code. Also what is said

Company Acknowledgements [was :Re: [HiveMind] 1.0 Beta]

[EMAIL PROTECTED] wrote: Once it goes beta, I'll start monitoring the user list as well as the developer list. Unless beta coincides with promotion to top level, in which case there will be a hivemind-user and hivemind-dev lists. WebCT will be getting back to me soon to finalize the wording for

Re: float ( 0.8 and 0.9 ) struts validator problem

flavio mendes rabelo wrote: Hi, I have the following problem. I need validate the type float. when i type values equal the 0.8 or 0.9 these values are not considered float number; but if I type y.8 or y.9 ( y > 0 ) or only .8 or .9 the validation is ok, the problem is whe I use the format x.8

Re: [validator] Password fields [WAS] Re: cvs commit: jakarta-commons/validator/src/javascript/org/apache/commons/validator/javascript validateMaxLength.js validateMinLength.js

David Graham wrote: The validation rules are only exposed if you use Struts' Not true they are exposed by server side validation also. The error messages clearly state the min/max values. I'm still -1 on this last commit for the reasons stated. Please revert this change to not validate pass

Re: [VOTE] New commons proper component - pcollections

Stephen Colebourne wrote: There is an additional point, in that [collections] is very widely dispersed and used. To increase its size by over 100% suggests that something should at least be looked at. This is not an issue. If a class is not used it will not be be loaded into the JVM. --

Re: [validator] Password fields [WAS] Re: cvs commit: jakarta-commons/validator/src/javascript/org/apache/commons/validator/javascript validateMaxLength.js validateMinLength.js

David Graham wrote: It is inherently insecure to reveal the specific details of password validation in client side scripting. Validator and Struts should be as secure as possible out of the box so I am -1 on this change. Please revert the changes until we come up with a better solution. Bugzill

Re: cvs commit: jakarta-commons/collections/src/java/org/apache/commons/collections/iterators ArrayListIterator.java

Phil Steitz wrote: jakarta-commons\collections\data\test seems to have test data with a version number. My guess is cloning the data and substuting NullComparator.version2.obj2 NullComparator.version3.obj Might work The changes to getCompatabilityVersion() below seem to be causing the compata

Re: cvs commit: jakarta-commons/digester/src/java/org/apache/commons/digester/plugins InitializableRule.java

[EMAIL PROTECTED] wrote: rdonkin 2003/10/04 05:27:37 Added: digester/src/java/org/apache/commons/digester/plugins InitializableRule.java I feel like the license police :-} but this is an Apache 1.0 license, eventhough it says version 1.1 compare it to the one

Re: cvs commit: jakarta-commons-sandbox/chain/src/java/org/apache/commons/chain/web/servlet/config ChainServlet.java

This is a Apache 1.0 License, The give away is it mentions 'Apache Group' [EMAIL PROTECTED] wrote: husted 2003/09/29 08:34:45 Added: chain/src/java/org/apache/commons/chain/web/servlet/config ChainServlet.java Log: Generic ChainSerlvet to allow loading a Cata

Re: [math] Maven build and elements of style

Brent Worden wrote: There are a few FIXME comments. I've configured my Eclipse to mark FIXMEs, but the out-of-the-box config highlights only TODOs. Can we agree on a common style here? I've been placing @todo messages inside javadoc comments. PRO: Maven can generate a task list report based o

Re: cvs commit: jakarta-commons-sandbox/resources build-legacy.xml build.xml

[EMAIL PROTECTED] wrote: rdonkin 2003/09/08 11:20:53 Modified:resources build.xml Added: resources build-legacy.xml Log: Replaced legacy build.xml with maven generated one Preferace: I am not a resources committer. I am happy with all the other many changes that you made, ex

Re: [HiveMind] releases

Howard M. Lewis Ship wrote: I'm going to add two more features and then call it beta. #1: Parameters for Interceptors. #2: resource translator (translators are used for conversions during XML to Java conversion). Since its in the sandbox, I don't believe I can or should put a release up on Apach

Re: [ANN] Commons-Validator 1.1.0 Alpha released

[EMAIL PROTECTED] wrote: Rob, one of my pet itches with validator is the lack of documentation/examples on the xml format. Can I help somehow with this? Yes, I am in heaven :-) ! Any time you want a break from Jira/Maven please feel free ! I always thought that reading the DTD and you're an

[ANN] Commons-Validator 1.1.0 Alpha released

Commons Validator 1.1.0 Alpha is now available for testing. Please refer to http://jakarta.apache.org/commons/validator/tasks.html that details some of the changes that have taken place since the 1.0.2 release. Downloads: http://jakarta.apache.org/~rleland/ValidatorAlpha/ Just a reminder : The rel

Re: [Vote] Release of Commons Validator

Robert Leland wrote: robert burrell donkin wrote: hi rob could you remember to cc the pmc next time? Thanks, and I will do that next time. I just sent out an email to [EMAIL PROTECTED] I ment to say [EMAIL PROTECTED] Thanks again, Rob every release needs to be approved and this is the

Re: [doc] release.html Feedback

Robert Leland wrote: How about RTFM. I see that these items are covered. :-} ! -Rob

[doc] release.html Feedback

I am going through the release process for Commons-Validator. After cutting the proposed release I took a look at the items marked 'LATER' There was some really good stuff/patches that were contributed that were rotting away. As a result I suggest adding a new Major Section Titled something li

Re: [Vote] Release of Commons Validator

x27;t subscribed to commons-dev get the chance to veto. BTW the usual convention in the commons is to prefix [RESULT] to emails of this kind. it makes it a bit easier for people to spot them. - robert On Tuesday, August 26, 2003, at 06:16 PM, Robert Leland wrote: I counted 2 +1 binding

Re: [Vote] Release of Commons Validator

fail to get +1 votes from non-project committers I include those from project committers and grumble about no one caring. Interesting difference in view :) Hen On Tue, 26 Aug 2003, Robert Leland wrote: I counted 2 +1 binding votes, and 1 +1 votes from another commons committer. I wil

Re: [Vote] Release of Commons Validator

I counted 2 +1 binding votes, and 1 +1 votes from another commons committer. I will cut the release tonight, test it, and upload it to the mirrors sometime this week. -Rob

Re: Release Process for Sandbox Projects

Leo Sutic wrote: From: Stephen Colebourne [mailto:[EMAIL PROTECTED] As a warning, my concerns would be the speed of passage through the sandbox. You need to think if you have a community to maintain this in commons proper, and whether people have had enough time to review it. My under

Re: [validator] Release 1.1.0

Arun Thomas wrote: I noticed that a vote is ongoing for release of validator. FYI, http://jakarta.apache.org/commons/dtds/validator_1_1.dtd should be updated to the version of the dtd currently in CVS. I don't know if this is a manual process, or something that happens automatically with the

[Vote] Release of Commons Validator

Commons Validator has recently undergone refactoring with a few bugs fixed and documentation updates. The following release plan is proposed for Validator 1.1.0: * /Tag Date/ - Tuesday, August 25, 2003, 23:59:59 * /Release Manager/ - Robert Leland * /Alpha Release Announcement/ - To the

Re: [resources] plans...?

Stephen Colebourne wrote: I have my own code at work that does resource management. From the quick look I took at [resources] it was more flexible, so in my dream world of infinite time to work on commons, I was going to add stuff to [resources]. Ideas include: - Main interface supports direct acc

Re: [Validator - Draft Release Proposal] Release of Commons Validator

David Graham wrote: --- Robert Leland <[EMAIL PROTECTED]> wrote: Validator Commons Committers I need your feedback. Commons Validator has recently undergone refactoring with a few bugs fixed and documentation updates. As of today the unit tests pass, and known existing application

Re: [docs] Crappy build system

he current confusing setup? We didn't have you to help us out before :-) ! Hen -- Robert Leland [EMAIL PROTECTED] -- Java, J2EE, Struts, Web Application Development 804 N. Kenmore Street +01-703-525-3580 Arl

Re: [vote] moving commons-sql, commons-dbcp and commons-dbutils todb.apache.org

Costin Manolache wrote: Robert Leland wrote: Costin Manolache wrote: Martin Poeschl wrote: as the name indicates db.apache.org is for db related projects. the db project is new but people will look for db related stuff there and not at jakarta-commons .. so it makes sense to move the

Re: [vote] moving commons-sql, commons-dbcp and commons-dbutils todb.apache.org

Costin Manolache wrote: Martin Poeschl wrote: as the name indicates db.apache.org is for db related projects. the db project is new but people will look for db related stuff there and not at jakarta-commons .. so it makes sense to move the projects to db.apache.com And people who are alread

Re: [jelly] move codebase to commons proper

Rodney Waldhoff wrote: Assuming you want the same directory structure under jakarta-commons you have under jakarta-commons-sandbox, simply executing: cp -r jakarta-commons-sandbox/jelly jakarta-commons/. should suffice to move the files and yet preserve the history. Later we can do a CVS remove

Re: [RESOURCES] Units tests rely on JDK 1.4

Robert Leland wrote: As with the cases in the mainline code, this was fixed in the 20030109 nightly build (i.e. last night's). I just did a CVS update ~4:45 P.M. EST, so it was fixed after that time ? Nope, not there. I just did another CVS update and ResourceBundleTestCase.java

Re: [RESOURCES] Units tests rely on JDK 1.4

Craig R. McClanahan wrote: On Thu, 9 Jan 2003, Robert Leland wrote: Date: Thu, 09 Jan 2003 17:09:48 -0500 From: Robert Leland <[EMAIL PROTECTED]> Reply-To: Jakarta Commons Developers List <[EMAIL PROTECTED]> To: Jakarta Commons Users List <[EMAIL PROTECTED]> Subject: [RESO

[RESOURCES] Units tests rely on JDK 1.4

Same as before but for Units tests. Locale(language), doesn't exist under JDK 1.3, only under 1.4. -Rob -- To unsubscribe, e-mail: For additional commands, e-mail:

[resources] depends on Java 1.4

Doesn't compile under Java 1.3. The constructor Locale(String language) Was introduced in JDK 1.4 Locale(String language, String country) Exists in 1.3 In impl/CollectionResourcesBase() -Rob -- To unsubscribe, e-mail: For additional commands, e-mail:

[resources]&new dependant [discovery] build problems.

In trying to build resources, I was unable to build it because the discovery junit tests failed on the jelly-plugin. I tried building discovery using both the commons-discovery maven build, and the commons maven build. It appears my top level build.properties for commons is current, but then again

Re: Conversion utilities

Henri Yandell wrote: On Thu, 14 Nov 2002, Jeff Varszegi wrote: Janek, I made an interface called Range that is supported by classes called ComparableRange etc. The ComparableRange class can use any objects that support Comparable (or, alternately, any objects with a supplied Comparator), and