Re: Migrating a resource adapter from glassfish to TomEE

2015-07-22 Thread Mike Spencer
I have found out how to set the JNDI name without specifying the ID attribute. I was messing around with the Tomcat REST API and I found out that it has a command to list all JNDI names for a class. I ran that with the ConnectionFactory I was using and found that it generated a default JNDI n

Re: Migrating a resource adapter from glassfish to TomEE

2015-07-22 Thread Mike Spencer
Hi Uday, That helps greatly. I was able to configure the properties I needed to this way. Is there a way of configuring a JNDI name for the ConnectionFactory via the system.properties? If I use the envContext.lookup("RA NAME") you provided I get a javax.resource.spi.ResourceAdapter implement

Re: Migrating a resource adapter from glassfish to TomEE

2015-07-21 Thread Uday Gire
Hi 1- To update resource adaptor ManagedConnectionFactory properties: - Open conf/system.properties file in TomEE, and add each managedconnectionfactory property in this file as: - RA_NAME.PROPERTY_NAME=PROPERTY_VALUE 2- To get the javax.resource.cci.ConnectionFactory instance, write the fol

Re: Migrating a resource adapter from glassfish to TomEE

2015-07-21 Thread Romain Manni-Bucau
Hmm, I dont have much time to check you exact setup and what is needed but here few pointers: - tomee.xml datasource are shared accross the server so RA should be able to lookup it - ra properties can be overwriten using system properties (ra name.property = value) - you can cast your ConnectionFa

Re: Migrating a resource adapter from glassfish to TomEE

2015-07-20 Thread Mike Spencer
Using class-name with the implementation worked, but it turns out that isn't what I needed. I am going to take a step back and try to describe what I am trying to do. I have a resource adapter packaged in a .rar file that includes the JCA implementation .jar and a ra.xml in the META-INF folder

Re: Migrating a resource adapter from glassfish to TomEE

2015-07-17 Thread Romain Manni-Bucau
2015-07-17 12:48 GMT-07:00 Mike Spencer : > Hi Romain, > > Using class-name allowed it to get past the 'Cannot determine a provider' > message, but now I am encountering a new error. > > This error occurs when using class-name"javax.resource.cci.ConnectionFactory"> in tomee.xml: > > class-name sh

Re: Migrating a resource adapter from glassfish to TomEE

2015-07-17 Thread Mike Spencer
Hi Romain, Using class-name allowed it to get past the 'Cannot determine a provider' message, but now I am encountering a new error. This error occurs when using class-name"javax.resource.cci.ConnectionFactory"> in tomee.xml: SEVERE: FATAL ERROR: Unknown error in Assembler. Please send the

Re: Migrating a resource adapter from glassfish to TomEE

2015-07-17 Thread Romain Manni-Bucau
Hi Using class-name in Resource declaration should make it. That said . = in conf/system.properties should work IIRC. Le 17 juil. 2015 20:32, "Mike Spencer" a écrit : > Hi all, > > I am trying to migrate an application using a resource adapter in a .rar > file from Glassfish to TomEE. The reso

Migrating a resource adapter from glassfish to TomEE

2015-07-17 Thread Mike Spencer
Hi all, I am trying to migrate an application using a resource adapter in a .rar file from Glassfish to TomEE. The resource adapter needs to be deployed globally (so multiple application can access it) and make the javax.resource.cci.ConnectionFactory implementation available via JNDI. I bel