From adffaces-dev-return-400-apmail-incubator-adffaces-dev-archive=incubator.apache.org@incubator.apache.org Tue Jul 11 14:55:02 2006 Return-Path: Delivered-To: apmail-incubator-adffaces-dev-archive@locus.apache.org Received: (qmail 88451 invoked from network); 11 Jul 2006 14:55:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 11 Jul 2006 14:55:01 -0000 Received: (qmail 12948 invoked by uid 500); 11 Jul 2006 14:54:53 -0000 Delivered-To: apmail-incubator-adffaces-dev-archive@incubator.apache.org Received: (qmail 12877 invoked by uid 500); 11 Jul 2006 14:54:53 -0000 Mailing-List: contact adffaces-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: adffaces-dev@incubator.apache.org Delivered-To: mailing list adffaces-dev@incubator.apache.org Received: (qmail 12841 invoked by uid 99); 11 Jul 2006 14:54:53 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Jul 2006 07:54:53 -0700 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=HTML_MESSAGE,NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [198.168.250.2] (HELO canada-smtp1.consulting.fujitsu.com) (198.168.250.2) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Jul 2006 07:54:50 -0700 Received: from Montreal-NS002.notes.dmr (montreal-ns002.notes.dmr [205.151.154.84] (may be forged)) by canada-smtp1.consulting.fujitsu.com (8.13.6/8.13.6) with ESMTP id k6BErufg006144 for ; Tue, 11 Jul 2006 10:53:56 -0400 To: adffaces-dev@incubator.apache.org Subject: Tr : (ADFFACES-44) does not allow EL for noMatchMessageDetail MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005 Message-ID: From: Simon_Lessard@DMR.CA Date: Tue, 11 Jul 2006 10:53:15 -0400 X-MIMETrack: Serialize by Router on Montreal-NS002/DMR/CA(Release 6.5.4|March 27, 2005) at 07/11/2006 10:54:19 AM, Serialize complete at 07/11/2006 10:54:19 AM Content-Type: multipart/alternative; boundary="=_alternative 0051E2F7852571A8_=" X-Proofpoint-Spam-Reason: safe X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --=_alternative 0051E2F7852571A8_= Content-Type: text/plain; charset="US-ASCII" Hello, I posted a patch for this issue, however it hsould not be closed yet as more validators have the same issues. Basically, I did the following to fix it: I added the following to RegExpValidator.java protected Object getNoMatchMessageDetailNoEval() { Object obj = _facesBean.getLocalProperty(_NO_MATCH_MESSAGE_DETAIL_KEY); if (obj != null) { return obj.toString(); } return _facesBean.getValueBinding(_NO_MATCH_MESSAGE_DETAIL_KEY); } and changed the call in _getNoMatchFoundMessage to use the previous method. The same strategy could be applied to most validator. Therefore, I was wondering if the getNoMatchMessageDetailNoEval would not benefit from being added to FacesBean instead as maybe public Object getUnevaluatedProperty or something like that. The method would simply return the local value if it exists, or the value binding without evaluating if it don't. Regards, Simon Lessard Fujitsu Consulting ----- Forwarded by Simon Lessard/NOTES on 2006-07-11 10:49 ----- "Simon Lessard (JIRA)" 2006-07-11 10:43 Please respond to adffaces-issues To: adffaces-issues@incubator.apache.org cc: Subject: [jira] Updated: (ADFFACES-44) does not allow EL for noMatchMessageDetail [ http://issues.apache.org/jira/browse/ADFFACES-44?page=all ] Simon Lessard updated ADFFACES-44: ---------------------------------- Status: Patch Available (was: Open) > does not allow EL for noMatchMessageDetail > --------------------------------------------------------------- > > Key: ADFFACES-44 > URL: http://issues.apache.org/jira/browse/ADFFACES-44 > Project: MyFaces ADF-Faces > Type: Bug > Reporter: Simon Lessard > > I copied this bug from OTN at http://forums.oracle.com/forums/message.jspa?messageID=1355472#1355472 > You cannot specify a noMatchMessageDetail using EL pointing on a resource file when using the tag. > The reproduction case is: > [code] > > > > > [/code] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --=_alternative 0051E2F7852571A8_=--