JBossJCA

What is JBossJCA?

 

A clean room implementation of the J2EE Connector API part of the J2EE specification.

JCA handles the deployment of resource adapters. These include DataSources and ConnectionFactorys and

MessageListeners to and from databases, legacy systems or JMS Servers

 

Spec

  • JBoss4 supports J2ee Connector API 1.5 (except JBoss4.0.0DR3)

  • JBoss3 supports J2ee Connector API 1.0

 

Features

 

  • Managed Connections

  • Automatic transaction enlistment

  • Security injection

  • Pooling

  • Local resource adapters can take part in two phase commit

  • DataSource deployment using any jdbc java.sql.Driver or javax.sql.XADataSource

  • JMS Resource Adapter

  • Dead connection checking

  • Prepared Statement pooling

  • No transaction, local and XA connection managers

  • Transaction inflow

  • Message inflow

  • Work management

  • Database failover

  • Lazy JCA Enlistment - a little known feature of JavaEE

 

Getting involved

Do you want to be a JBossJCA committer? Take a look at the [currently outstanding tasks in

JIRA|http://jira.jboss.com/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12310093]

 

Architecture

 

 

Configuration

 

 

Forums

 

 

Examples

 

Authors

 

 

Retired

  • David Jencks

  • Andrey Demchenko

  • Igor Fedorenko

  • Jason Dillon

  • Norbert Lataille

  • Erwin Guib

  • Toby Allsopp

  • And many patches gratefully received from the community with thanks.

 

Old Change Notes

 

Related