What is JBossJCA?
MessageListeners to and from databases, legacy systems or JMS Servers
JBoss4 supports J2ee Connector API 1.5 (except JBoss4.0.0DR3)
JBoss3 supports J2ee Connector API 1.0
Automatic transaction enlistment
Local resource adapters can take part in two phase commit
DataSource deployment using any jdbc java.sql.Driver or javax.sql.XADataSource
Dead connection checking
Prepared Statement pooling
No transaction, local and XA connection managers
Lazy JCA Enlistment - a little known feature of JavaEE
Do you want to be a JBossJCA committer? Take a look at the [currently outstanding tasks in
Overview - a brief overview of the architecture
Source Tree - a brief overview of the source tree
Pooling - overview of pooling
Lazy AutoCommit Optimization - reducing the traffic to the server
General - General JCA config including the resource adapter deployer
Deploying DataSources and ConnectionFactorys - deploying -ds.xml files
Common - Common parameters for datasources and connection factories
DataSources - Configuring a datasource
ConnectionFactory - Configuring connection factories (connection-definitions in 1.5)
JCA Login Modules - Injecting security configuration into connection creation
Encrypting DataSource Passwords How to encrypt DataSource passwords
Inbound - Configuring a MessageListener for an inbound resource adapter (jca 1.5)
InboundJavaMail - Configuring a MessageListener for an inbound emails (jca 1.5)
Admin Objects - Admin Objects (jca 1.5)
DebugConnectionProblems - an overview of what to look at
FAQ frequently asked questions
The development forum is for the discussion of changes to the implementation.
Bug Reports, Change Notes and RoadMap to find solved problems, known issues or report new problems
WestonPrice project lead.
And many patches gratefully received from the community with thanks.
Old Change Notes