Return-Path: Delivered-To: apmail-beehive-dev-archive@www.apache.org Received: (qmail 61904 invoked from network); 3 May 2006 18:37:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 3 May 2006 18:37:26 -0000 Received: (qmail 51638 invoked by uid 500); 3 May 2006 18:37:25 -0000 Delivered-To: apmail-beehive-dev-archive@beehive.apache.org Received: (qmail 51605 invoked by uid 500); 3 May 2006 18:37:24 -0000 Mailing-List: contact dev-help@beehive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Beehive Developers" Delivered-To: mailing list dev@beehive.apache.org Received: (qmail 51594 invoked by uid 99); 3 May 2006 18:37:24 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 May 2006 11:37:24 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 May 2006 11:37:23 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 96CEC714292 for ; Wed, 3 May 2006 18:36:47 +0000 (GMT) Message-ID: <19273734.1146681407615.JavaMail.jira@brutus> Date: Wed, 3 May 2006 18:36:47 +0000 (GMT+00:00) From: "Eddie O'Neil (JIRA)" To: dev@beehive.apache.org Subject: [jira] Commented: (BEEHIVE-1070) bindingUpdateErrors expression="${aValue}" always returns tag error In-Reply-To: <777286487.1140215190881.JavaMail.jira@ajax.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/BEEHIVE-1070?page=comments#action_12377608 ] Eddie O'Neil commented on BEEHIVE-1070: --------------------------------------- Krista -- after looking at this, I think that the documentation is incorrect. This tag's "expression" attribute should resolve to a NetUI expression because it's specified in the tag as: or because the container executes a JSP 2.0 expression whose value is a NetUI expression: <% pageContext.setAttribute("theexpression", "actionForm.foo");%> The exception is caused because the "expression" attribute requires a value. Iroincally, I think that the real bug is that the tag should have runtime expressions disabled. I'll make both of these changes -- disabling runtime expressions and the documentation fix. > bindingUpdateErrors expression="${aValue}" always returns tag error > ------------------------------------------------------------------- > > Key: BEEHIVE-1070 > URL: http://issues.apache.org/jira/browse/BEEHIVE-1070 > Project: Beehive > Type: Bug > Components: NetUI > Versions: 1.0.1 > Reporter: Krista Baker > Fix For: v.next > > As listed in the JSP tag documentation, the following tag will always produce a tag error > > with a message of: Attribute 'expression' is required to have a value. The value "" is illegal. This is often caused by binding to an object with a null value. > If the above expression="${actionForm.firstName}" is changed to "actionForm.firstName", the expected behavior will be observed. > The netui test of coretags/binding/nullbinding is an example of this where the error is seen only because the expression="${ }". > From this index.jsp: >
  • -- Binding Errors
  • > Even though the value remains null, if the expression is changed to the following, >
  • -- Binding Errors
  • > the error will not occur even though the pageFlow value is still null. > There are three netui testRecorder tests that use this element and attribute combination: > coretags/binding/nullbinding - uses expression="${}" > coretags/binding/report - uses expression="" > tags/bindingUpdateErrors - uses expression="" > I am not sure if the example in the docs (http://beehive.apache.org/docs/1.0.1/netui/apidocs/taglib/beehive.apache.org/netui/tags-html-1.0/bindingUpdateErrors.html) and the nullbinding test are incorrect or if it is the other way around that the other two tests, even though currently producing expected results, are wrong. -- 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