You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2003/07/17 19:19:49 UTC
DO NOT REPLY [Bug 21693] New: -
copyProperties method should not exit as soon as it gets Exception
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=21693>.
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=21693
copyProperties method should not exit as soon as it gets Exception
Summary: copyProperties method should not exit as soon as it gets
Exception
Product: Commons
Version: Nightly Builds
Platform: All
OS/Version: All
Status: NEW
Severity: Enhancement
Priority: Other
Component: Bean Utilities
AssignedTo: commons-dev@jakarta.apache.org
ReportedBy: apache@ianhowlett.com
The copyProperties method in BeanUtils.java currently has trouble with EJBs
because it exits as soon as an Exception is raised (often a
java.lang.reflect.InvocationTargetException).
Rather than exiting the method and throwing the Exception to the caller, the
method should give a choice to swallow the exception for this field and move on
to attempting the next field.
This is trivial at the coding stage, requiring just a try/catch block inside the
'for' loop. Perhaps more tricky is designing the API to cope with this behavior
whilst retaining backwards compatibility.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org