DO NOT REPLY [Bug 27861] New: - Add better error reporting to bean:define tag

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27861>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=27861

Add better error reporting to bean:define tag

           Summary: Add better error reporting to bean:define tag
           Product: Taglibs
           Version: unspecified
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Unknown Taglib
        AssignedTo: taglibs-dev@jakarta.apache.org
        ReportedBy: apache@rainking888.endjunk.com


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.

---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org