[ https://issues.apache.org/jira/browse/BEANUTILS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Niall Pemberton resolved BEANUTILS-263. --------------------------------------- Resolution: Fixed Assignee: Niall Pemberton > Improve ClassConverter robustness > --------------------------------- > > Key: BEANUTILS-263 > URL: https://issues.apache.org/jira/browse/BEANUTILS-263 > Project: Commons BeanUtils > Issue Type: Improvement > Components: ConvertUtils & Converters > Affects Versions: 1.7.0 > Reporter: Alex Albu > Assignee: Niall Pemberton > Priority: Minor > Fix For: 1.8.0 > > Attachments: ClassConverter.java.patch.txt > > > To load a class by name, ClassConverter attempts to use (in order) the > current thread's context class loader and the class loader that loaded the > class itself. But in my opinion it is a little inconsistent in the way it > does it. Basically, it will use the second class loader as a fallback *only* > if the first one (context class loader) is not set (null). That causes the > converter to fail in environments where the context class loader is set but > does not have access to the class it's trying to load (Weblogic 9.2 is an > example). > I think a more robust behavior would be to try the second class loader *any* > time using the context one fails (be it because it's not set, or it cannot > load the class for some reason). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]