Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 85617 invoked from network); 4 Feb 2003 00:43:52 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 4 Feb 2003 00:43:52 -0000 Received: (qmail 12870 invoked by uid 97); 4 Feb 2003 00:45:26 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@nagoya.betaversion.org Received: (qmail 12863 invoked from network); 4 Feb 2003 00:45:26 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 4 Feb 2003 00:45:26 -0000 Received: (qmail 85418 invoked by uid 500); 4 Feb 2003 00:43:49 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 85407 invoked from network); 4 Feb 2003 00:43:49 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 4 Feb 2003 00:43:49 -0000 Received: (qmail 12857 invoked by uid 50); 4 Feb 2003 00:45:23 -0000 Date: 4 Feb 2003 00:45:23 -0000 Message-ID: <20030204004523.12856.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: commons-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 16744] New: - Allow special positioning of error messages X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16744 Allow special positioning of error messages Summary: Allow special positioning of error messages Product: Commons Version: 1.0 Final Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Validator AssignedTo: commons-dev@jakarta.apache.org ReportedBy: peteroldershaw@comcast.net We have identified a case when it would be handy if you could set the key for a validation in the configuration file. Unfortunately, the key is replaced by generateKey when it is called. It would be nice if it did not generate a key if one already existed. Why? That way you can create two different validations for the same field and have them displayed at different places on the screen. e.g. A message like "You must have at least one item in your cart" could be given a different key and then displayed at the top of the page using the errors tag while the same field could have a format validation and have the errors tag next to it on the page. I hope this makes sense as it is a little hard to explain. Send me an email if you need more. Thanks...Peter --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org