| org.springframework.beans.factory.FactoryBean that creates
a local JCA connection factory in "non-managed" mode (as defined by the
Java Connector Architecture specification). This is a direct alternative
to a
org.springframework.jndi.JndiObjectFactoryBean definition that
obtains a connection factory handle from a J2EE server's naming environment.
The type of the connection factory is dependent on the actual connector:
the connector can either expose its native API (such as a JDBC
javax.sql.DataSource or a JMS
javax.jms.ConnectionFactory )
or follow the standard Common Client Interface (CCI), as defined by the JCA spec.
The exposed interface in the CCI case is
javax.resource.cci.ConnectionFactory .
In order to use this FactoryBean, you must specify the connector's
LocalConnectionFactoryBean.setManagedConnectionFactory "managedConnectionFactory" (usually
configured as separate JavaBean), which will be used to create the actual
connection factory reference as exposed to the application. Optionally,
you can also specify a
LocalConnectionFactoryBean.setConnectionManager "connectionManager" ,
in order to use a custom ConnectionManager instead of the connector's default.
NOTE: In non-managed mode, a connector is not deployed on an
application server, or more specificially not interacting with an application
server. Consequently, it cannot use a J2EE server's system contracts:
connection management, transaction management, and security management.
A custom ConnectionManager implementation has to be used for applying those
services in conjunction with a standalone transaction coordinator etc.
The connector will use a local ConnectionManager (included in the connector)
by default, which cannot participate in global transactions due to the lack
of XA enlistment. You need to specify an XA-capable ConnectionManager in
order to make the connector interact with an XA transaction coordinator.
Alternatively, simply use the native local transaction facilities of the
exposed API (e.g. CCI local transactions), or use a corresponding
implementation of Spring's PlatformTransactionManager SPI
(e.g.
org.springframework.jca.cci.connection.CciLocalTransactionManager )
to drive local transactions.
author:
Juergen Hoeller
since:
1.2
See Also: LocalConnectionFactoryBean.setManagedConnectionFactory
See Also: LocalConnectionFactoryBean.setConnectionManager
See Also: javax.resource.cci.ConnectionFactory
See Also: javax.resource.cci.Connection.getLocalTransaction
See Also: org.springframework.jca.cci.connection.CciLocalTransactionManager | 