[ http://issues.apache.org/jira/browse/BEANUTILS-189?page=comments#action_12448003 ] Henri Yandell commented on BEANUTILS-189: -----------------------------------------
I'm +1 to WONTFIX on this one. I don't see an option to ignore failures as being of much value. That said - I don't get why EJBs would cause more failures. Am I missing something? > [beanutils] copyProperties method should not exit as soon as it gets Exception > ------------------------------------------------------------------------------ > > Key: BEANUTILS-189 > URL: http://issues.apache.org/jira/browse/BEANUTILS-189 > Project: Commons BeanUtils > Issue Type: Improvement > Components: Bean / Property Utils > Affects Versions: Nightly Builds > Environment: Operating System: All > Platform: All > Reporter: Ian Howlett > Priority: Minor > > 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/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]