[ http://issues.apache.org/struts/browse/STR-2019?page=all ]
David Evans closed STR-2019:
----------------------------
Resolution: Fixed
> [taglib] Add better error reporting to bean:define tag
> ------------------------------------------------------
>
> Key: STR-2019
> URL: http://issues.apache.org/struts/browse/STR-2019
> Project: Struts Action 1
> Type: Improvement
> Components: Taglibs
> Versions: Unknown
> Environment: Operating System: other
> Platform: All
> Reporter: Doug Daniels
> Assignee: David Evans
> Priority: Minor
> Fix For: 1.2.8
>
> The bean:define tag in the Struts Bean taglib could use better error
> reporting.
> It is extremely difficult to debug the common error of trying to define a bean
> that is actually null (say, for example, if you typed the name incorrectly).
> Whenever bean:define tries to set a value that is null, it errors out with the
> following message:
> [ServletException in:/WEB-INF/components/Test.jsp] Define tag cannot set a
> null
> value']
> If you have more than one bean:define tag in your JSP, you can't even tell
> which
> one is generating the error. This makes the debugging process incredibly
> laborious.
> The gains from a simple addition to the error message (such as 'for bean with
> id=x') would be huge. Is this possible?
> If possible, the gains from a more complex error reporting that was aware of
> where a null value occurred (at which point in the name.property chain) would
> be
> even larger.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
