tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 29200] New: - Better error message when instantiation of abstract page fails
Date Tue, 25 May 2004 10:09:35 GMT
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=29200>.
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=29200

Better error message when instantiation of abstract page fails

           Summary: Better error message when instantiation of abstract page
                    fails
           Product: Tapestry
           Version: 3.0
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Framework
        AssignedTo: tapestry-dev@jakarta.apache.org
        ReportedBy: filip@stubkjaer-adamsen.dk


Pages are often declared abstract to allow Tapestry to enhance them. But when 
Tapestry sees no need to do so, because a Page does not need enhancement, an 
InstantiationException will be thrown. The corresponding error message -
 "Unable to instantiate an instance of class [class-name]" - confuses many 
developers, and should instead state something like: "Unable to instantiate an 
instance of class [class-name]: The class is abstract, but does not need 
enhancement." This would allow developers to quickly fix the problem.

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


Mime
View raw message