commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 16233] New: - Invalid bean setters do not generate an exception
Date Sat, 18 Jan 2003 08:39:53 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16233>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16233

Invalid bean setters do not generate an exception

           Summary: Invalid bean setters do not generate an exception
           Product: Commons
           Version: 1.3 Final
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Digester
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: me@howardmiller.co.uk


In particular, when using the addBeanPropertySetter method of the Digester (but
probably with other similar methods). The second parameter describes the name of
the bean property from which the setter method is generated. If this method is
not present in the bean, Digester does NOT generate any kind of exception or
notification. This is easily done by (for example) using an upper case charater
in place of a lower for the bean property name.

Digester should generate and exception when a rule is fired, and the bean setter
method is not found in the bean.

--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message