Several problems are causing MDB deployment to fail:
- Deployment states that ActivationSpec attributes do not exist.. but they do. Seems like a case problem with the letter of the attribute name.
Fixed this by using Introspector.decapitalize(...) in the MdbBuild to fix attribute name.
- The resource-link from the mdb to the resource adapter is resulting in: Server reports: Unknown or ambiguous resource name query: geronimo.server:j2eeType=JCAResourceAdapter,J2EEServer=geronimo,J2EEApplication=null,name=SampleActiveMQResourceAdapter,* match count: 0.
Fixed this adjusting the RefContext to use the resourceAdapterIndex map instead of the connectionFactoryIndex to lookup the resourceAdapater.