beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eddie O'Neil (JIRA)" <>
Subject [jira] Commented: (BEEHIVE-1070) bindingUpdateErrors expression="${aValue}" always returns tag error
Date Wed, 03 May 2006 18:36:47 GMT
    [ ] 

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:

  <netui:bindingUpdateErrors expression=""/>

or because the container executes a JSP 2.0 expression whose value is a NetUI expression:

  <% pageContext.setAttribute("theexpression", "");%>
  <netui:bindingUpdateErrors expression="${theexpression}"/>

The exception is caused because the "expression" attribute requires a value.  Iroincally,
I think that the real bug is that the <bindingUpdateErrors> 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:
>      Project: Beehive
>         Type: Bug

>   Components: NetUI
>     Versions: 1.0.1
>     Reporter: Krista Baker
>      Fix For:

> As listed in the JSP tag documentation, the following tag will always produce a tag error

> <netui:bindingUpdateErrors expression="${actionForm.firstName}"/>
> 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:
>   <li><netui:bindingUpdateErrors expression="${pageFlow.nullValue}" /> --
Binding Errors</li>
> Even though the value remains null, if the expression is changed to the following, 
>   <li><netui:bindingUpdateErrors expression="pageFlow.nullValue" /> -- Binding
> 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 (
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:
For more information on JIRA, see:

View raw message