1) Deploy the resource-adapter to the instance
2) Create pool and resource with "target" as the instance
3) Deploy the application that uses the resources of the
resource-adapter to the instance.
[This will fail in DAS as there seem to be some processing happening in
DAS though the target is "instance"]
Exact failure is due to EjbBundleValidator making sure that the
resource-type of the resource-ref specified is valid.
[Refer EJBBundleValidator calling "resRef.checkType()" in the method
Above check will fail in DAS as the resource-adapter is not enabled (and
hence not available for the classloader hierarchy).
Workaround would be to deploy the resource-adapter and the application that uses the resource-adapter in DAS and then create application-ref in appropriate targets.