I've researched the previous posts on this subject and my application seems in order.
I've created a database connection applying a connection pool and JNDI reference via the application server. These test out just fine. They appear in the JNDI browser as:
BPELSamples eis/DB/BPELSamples oracle.tip.adapter.db.DBConnectionFactory
DBConnection1 eis/DB/DBConnection1 oracle.tip.adapter.db.DBConnectionFactory
flmis eis/DB/flmis oracle.oc4j.sql.ManagedDataSource
Olite eis/DB/Olite oracle.tip.adapter.db.DBConnectionFactory
I can see this reference in the data-sources.xml (under j2ee ...)
<managed-data-source connection-pool-name="BPEL_APP_CONNECTION_POOL" jndi-name="eis/DB/flmis" name="flmist1"/>
<connection-pool name="BPEL_APP_CONNECTION_POOL">
<connection-factory factory-class="oracle.jdbc.pool.OracleDataSource" user="flbpel" password="******" url="jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=tcp)(HOST=10.40.5.18)(PORT=20061)))(CONNECT_DATA=(SERVICE_NAME=flmist1)))"/>
</connection-pool>
So all seems in order. Data is persisted, however I get the following log message when I execute my process on the development server:
<2007-05-18 10:46:22,306> <INFO> <test.collaxa.cube.ws> <AdapterFramework::Outbound> Since unable to locate the JCA Resource Adapter deployed at 'eis/DB/flmis', will then attempt to instantiate ManagedConnectionFactory oracle.tip.adapter.db.DBManagedConnectionFactory directly.
I'm assuming that the information generated in the db adaptor wizard is picking up the extra non-JNDI information and effecting the database update/insert. If this is the case then I'm going to have problems when this process migrates to the test server where I expect the JDNI reference to offer a level of indirection to the appropriate test database.
Where am I going wrong?