Java Code Examples for

Following code examples demonstrate how to use spring-framework. These examples are extracted from various highly rated open source projects. You can directly use these code snippets or view their entire linked source code. These snippets are extracted to provide contextual information about how to use this class in the real world. These samples also let you understand some good practices on how to use various code implementation of this class.

	public LocalConnectionFactoryBean tuxedoConnectionFactoryBean() {
		LocalConnectionFactoryBean lcfb = new LocalConnectionFactoryBean();

		return lcfb;

	public void test() throws ResourceException {

		LocalConnectionFactoryBean b = new LocalConnectionFactoryBean();

		ConnectionManager connectionManager = null;
		ManagedConnectionFactory managedConnectionFactory = null;




    public LocalConnectionFactoryBean jcrRepository(ManagedConnectionFactory connectionFactory, TransactionManager arjunaTransactionManager) throws SystemException {
        LocalConnectionFactoryBean factoryBean = new LocalConnectionFactoryBean();
        factoryBean.setConnectionManager(new XAConnectionManager(arjunaTransactionManager));
        return factoryBean;

org.springframework.beans.factory.FactoryBean that creates a local JCA connection factory in "non-ma

naged" 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 Java EE 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 #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 #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 specifically not interacting with an application server. Consequently, it cannot use a Java EE 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 #setManagedConnectionFactory @see #setConnectionManager @see javax.resource.cci.ConnectionFactory @see javax.resource.cci.Connection#getLocalTransaction @see org.springframework.jca.cci.connection.CciLocalTransactionManager

Read More