Want to get the Tuxedo adapter going outside a container in Spring via the Spring JCA CCI (http://static.springsource.org/spring/docs/3.2.0.M2/reference/html/cci.html). Not much experience with JCA but got the basic idea.

The resource adapter is the glue for the domain configuration, debug levels and so forth. Started by using the TuxedoClientSideResourceAdapter and registering it to the TuxedoAdapterSupervisor singleton that is used by the TuxedoManagedConnectionFactory. Spring JCA CCI represents the local connection factory inside the LocalConnectionFactoryBean which needs the TuxedoConnectionFactory built by the TuxedoManagedConnectionFactory:

Expected to see more detailed information about what is going on in the TJASerivce when setting up the context. Which isn't happening due to how I am not correctly rigging Spring. So how to get tracing/debug working? Or can it be that printing via the JUL logger isn't working. Got in my logging.properties file FINEST on everything oracle and weblogic.

FINEST is definately set for everything Oracle. Plus in the resource adapter I set everything to debug. Weird thing is that the JCA adapter writes out to a "tuxedo" text file in the execution directory. Mimics some of the console data. I am getting some tracing but not complete (from what I have seen on other forum posts).

There is a bunch of Spring stuff mixed in but the main idea is to wrap the Connection Factory in a template bean (CciTemplate) that eats a Tuxedo interaction specification and handles the start/stop of the connection plus execution. Nowhere in the configuration are resources or the local/remote resource sessions identified. The Oracle documentation says that with the client side the container is responsible for defining resources. Great. How? ;-) Tried doing it by hand:

After rereading the Oracle documentation concerning the 3 ways of defining the configuration (xml, factory and client-side) I tested the regular Resource Adapter (RA) with XML and the factory/client-side through their RA properties. All 3 methods update the configuration manager when the RA is registered via the supervisor when Spring issues a call to the start method when the ResourceAdapterFactoryBean is created (afterSetProperties call). So I should have a configuration regular of which RA implementation I choose. However, the setup stills fails in the TuxedoInteraction.doTPCall with a NullPointer exception. Assuming the problem is still down in the TuxedoConnection implementation.

Small step further. Went back to a problem with the TJAService startup whereby I was getting a naming exception. Something with create subcontexts so I added a Spring SimpleNamingContextBuilder to define a default context. That elevated the TJAService 072 fatal. Which resulted in a different failure not a Null pointer exception:
org.springframework.dao.DataAccessResourceFailureException: CCI operation failed; nested exception is javax.resource.ResourceException: TPCALL failed TPException:TPENOENT(6):0:0:TPED_MINVAL(0):QMNONE(0):0:No local or remote domain available for TOUPPER

Caused by: javax.resource.ResourceException: TPCALL failed TPException:TPENOENT(6):0:0:TPED_MINVAL(0):QMNONE(0):0:No local or remote domain available for TOUPPER
at com.oracle.tuxedo.adapter.cci.TuxedoInteraction.doTPCall(TuxedoInteraction.java:1019)
at com.oracle.tuxedo.adapter.cci.TuxedoInteraction.execute(TuxedoInteraction.java:407)
at org.springframework.jca.cci.core.CciTemplate$2.doInInteraction(CciTemplate.java:276)
at org.springframework.jca.cci.core.CciTemplate$1.doInConnection(CciTemplate.java:217)
at org.springframework.jca.cci.core.CciTemplate.execute(CciTemplate.java:194)
... 32 more