Hi Anthony, thanks for your reply.
The problem isn't regarding the development of a JCA Resource Adapter, but about configuring and referencing it in Tomee. I see, the id-attributes in the ra.xml are neccessary to create the corresponding resources in the JNDI-Namespace. Next, I see, that there is an undocumented way to create Per-App-Instances of a Resource via <Resource ... class="..."> (rather than type="...", as documented at the Tomee Site). But without packaging both the WAR and the RAR in one EAR and deploying this EAR, a Resource Adapter that provides it's own Connection/ConnectionFactory Interfaces cannot be effectively used in Tomee due to classloading issues. Looking forward to Java EE 7 (with JCA 1.7) Support in Tomee soon, to get a clarified, streamlined and well documented, yet specified way to registering connections via @ConnectionFactoryDefinition and instances via @AdminObjectDefinition. As a sad conclusion: for me, there is no reason to use Tomee for Full-Profile-Enterprise-Apps, until Tomee supports JCA 1.7. Thats why, we consult our customers to go with Wildfly 8.x rather than with Tomee. Robert -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/Please-provide-a-working-example-for-configuring-any-kind-of-resource-adapters-in-tomee-tp4673033p4673068.html Sent from the TomEE Users mailing list archive at Nabble.com.
