> Hi Romain, > > thanks for your help, but it won't work. > > For Example: > > I try to use the Files-Connector from Adam Bien > (http://connectorz.adam-bien.com). > > - unpack the rar > - add a ra.xml with: > > > > - repack the rar and deploy it to tomee, results in: > > > > - create a test.war application with a startup singleton: > > > > - deploy the test.war results in the following log: > > > > So as a resume: > > The RA is deployed and the ConnectionFactory (BucketStore) is created with > id=filesCXF but this connection is not injected in the @Resource(name = > "filesCXF") BucketStore store. > > While the Session-Context-Lookup returns an instance of FileBucketStore > (which implements BucketStore), a cast to BucketStore fails. Which leads to > classloader-problems. > > Both the files-connector.rar and the test.war contains the > files-connector-api.jar. This API-Jar contains the BucketStore.class > (Interface). > > This is really weird! >
Not that much: api jar is not shared so you don't use the same class. You can extract this api jar, put it in tomee and remove it from the war and rar. > Why Tomee does it in it's own way? Why isn't this documented? Why can't I > define my own JNDI-Name for the connection to be looked up as I can do it in > other Application Servers? > It is documented by JVM classloader behavior ;). About JNDI names I guess that's just because we use id directly but using activemq samples you can find anywhere you can surely do it using <Resource /> as I described before. In any case that's something not that hard to enhance we'll tackle on the road to EE 7 in the worse case. > 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-tp4673033p4673048.html > Sent from the TomEE Users mailing list archive at Nabble.com.
