RARDeployment throws incorrect IllegalArgumentException for underlying ManagedConnectionFactory exceptions

In org.jboss.resource.connectionmanager.RARDeployment.setManagedConnectionFactoryAttribute(String name, Class clazz, Object value, boolean mustExist)

try
{
setter.invoke(mcf, new Object[]

{value}

);
log.debug("set property " + name + " to value " + value);
}
catch (Exception e)
{
String error = "Unable to invoke setter method '" + setter + "' " + "on object '" + mcf + "'";
if (mustExist)
throw new IllegalArgumentException(error);
else

{ log.trace(error); return; }

}

When ANY exception is caught from an invocation of the ManagedConnectionFactory's setter method an IllegalArgumentException is thrown. This can be misleading depending on the actual exception thrown from the ManagedConnectionFactory's setter (see SalesForce case#00003103).

Either the underlying exception should be wrapped in a org.jboss.resource.JBossResourceException and thrown or the underlying exception should be logged inline or both. In the case of an InvocationTargetException the target exception could be wrapped/logged/etc.