There are two main issues as I understand it:
1) First, the resource adapter class has multiple setters for the same property and a getter for that property that returns a primitive type. The ConnectorModuleBuilder.setUpDynamicGBean() sets up a dynamic gbean with attribute types based on the return types of the getter methods and the ConnectorModuleBuilder.getValue() tries to convert the property value specified in the deployment descriptor into the value of expected type. Now, since the expected type is a primitive type, the classLoader.loadClass fails. That explains the initial "Could not load attribute class: type: int" error.
The simplest solution for this problem is to map all the primitive types into their corresponding complex types.
2) The second problem, after fixing the first issue, is that connector deployment might fail with "java.lang.ClassCastException" errors while setting the attributes on the dynamic gbean. The problem is in DynamicGBeanDelegate.java. It creates a separate propertyName->operation map for all getters and all setters. The problem arises if there are multiple setters for the same property. Only the last setter method discovered will be stored in the setters map. So, when an attribute is being set (using the setAttribute() method) a wrong setter method might be used for the value (type) being passed. That explains the "java.lang.ClassCastException" errors.
The solution for that problem is to change DynamicGBeanDelegate.java to support multiple setters and to pick the right setter based on the type of the value passed in when setting an attribute on the dynamic gbean.