Return-Path: Delivered-To: apmail-jakarta-jetspeed-dev-archive@www.apache.org Received: (qmail 58309 invoked from network); 28 Jan 2005 15:11:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 28 Jan 2005 15:11:39 -0000 Received: (qmail 97149 invoked by uid 500); 28 Jan 2005 15:11:30 -0000 Delivered-To: apmail-jakarta-jetspeed-dev-archive@jakarta.apache.org Received: (qmail 96879 invoked by uid 500); 28 Jan 2005 15:11:28 -0000 Mailing-List: contact jetspeed-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jetspeed Developers List" Reply-To: "Jetspeed Developers List" Delivered-To: mailing list jetspeed-dev@jakarta.apache.org Received: (qmail 96848 invoked by uid 99); 28 Jan 2005 15:11:28 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from Unknown (HELO FBISRV01.hq.freebalance.com) (142.46.199.82) by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 28 Jan 2005 07:11:27 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C5054B.A1A58EEE" Subject: Error messages for Security Forms hard coded Date: Fri, 28 Jan 2005 10:11:24 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Error messages for Security Forms hard coded Thread-Index: AcUFS6Dc2e9WwdvJTsy+ZduHNbNadA== From: "Mehdi Bennani" To: Cc: X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N ------_=_NextPart_001_01C5054B.A1A58EEE Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hey Folks,=20 =20 We have implemented our UserManagement, groupManagement and roleManagement security classes as per the jetpseed interfaces provided. It is all working fine, except that the messages returned when there is any failure are all hard-coded and coming from the SecurityConstants class string array. This poses a problem, not only for localization but also prevents us from displaying the right message to the user. =20 Example: if the admin tries to create a user with an invalid email address according to some password policy, we would like to inform the admin: "Error: password not conform to policy XYZ...". But instead we get the generic: "Invalid Entity Name. Please enter a valid entity name." =20 Are you thinking of changing that in the future? And, in the meantime, is there a way to access the context from our UserManagement class and put in the right message? Something like: context.put(SecurityConstants.PARAM_MSG, "Error: password not conform to policy XYZ"); =20 And would that be enough? Wouldn't that context value be overwritten afterwards from the Security Action class? =20 =20 Thank you a bunch, Mehdi-- =20 ------_=_NextPart_001_01C5054B.A1A58EEE--