[ http://issues.apache.org/jira/browse/BEEHIVE-429?page=history ]
Eddie O'Neil resolved BEEHIVE-429:
----------------------------------
Assign To: Krista Baker
Resolution: Won't Fix
Unfortunately, there's not an awful lot that NetUI can do here. Because the
expression is in the JSP 2.0 EL, the container will evaluate it and pass the
result to a setter on a JSP tag. This means that the tag knows neither the
expression nor whether it evaluated to "null" because the object was null or
wasn't found.
Given this, the <netui:content> tag is really doing all it can here by warning
that "null" was encountered.
> appbash031005 - Improve error message for invalid expressions
> -------------------------------------------------------------
>
> Key: BEEHIVE-429
> URL: http://issues.apache.org/jira/browse/BEEHIVE-429
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: V1Beta
> Reporter: David Madrid
> Assignee: Krista Baker
> Priority: Minor
> Fix For: V1
>
> - Improve the error message you get when you have an invalid expression that
> resolves to null in one of your netui tags, such as <netui:content
> value="${requestScopeWRONG.data.name}"/>. Here's the error message you get
> in the console:
> 10 Mar 2005 13:11:29,441 WARN Content []: Content: expression null
> reso
> lved to null, using empty string.
>
> - Test Case:
> 1.- Create a JSP using the <netui:content> tag with a bad expression
> value:
> <netui:content value="${requestScopeMISSPELLED.data.name}"/>
> 2.- When you hit the jsp from browser, the page is displayed fine (with
> no value for the tag), but you get this error in the console:
> "10 Mar 2005 13:11:29,441 WARN Content []: Content: expression null
> reso
> lved to null, using empty string."
>
> - Expected Results:
> To help troubleshooting, it might be nice to have the error message
> tell you what JSP it is referring to and where in the JSP the error is
> occuring (line number).
> - Actual Results:
> You get the error message above.
> - Root Cause:
> UNKNOWN
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
