2. What’s Next for the Java EE
Connector Architecture
Sivakumar Thyagarajan (Oracle), Jesper
Pedersen (RedHat), Fred Rowe (IBM)
BOF 7904 – JavaOne San Francisco 2013
19. Java EE Connector Architecture 2.0
Change the existing architecture
But keep the overall concepts
Apply modern programming approach
Use generics
Support JSR-330 injection
Simplify concepts
Clear separation of SPI contracts
Remove the notion of a “common” client interface
20. Java EE Connector Architecture 2.0
New architecture
Only have the vendor implement the required contracts
NoTransaction
LocalTransaction
XATransaction
Provide marker interfaces for contracts
javax.jca.spi.client.Connection
javax.jca.spi.client.ConnectionFactory
javax.jca.spi.management.AdministeredObject
Remove unused / “deprecated” functionality
LogWriter – replaced by java.util.logging
Common Client Interface (CCI)
21. Java EE Connector Architecture 2.0
Support JSR-330 for injection
BootstrapContext
ResourceAdapter
TransactionSynchronizationRegistry
WorkManager
XATerminator
Validator
23. Java EE Connector Architecture 2.0
ConnectionManager
Allow the resource adapter to destroy ManagedConnection's
boolean
destroyManagedConnections(ManagedConnectionFactory, Subject, C
onnectionRequestInfo)
Lazy ConnectionManager
Allow the resource adapter to tell when it doesn't need the
ManagedConnection
25. Java EE Connector Architecture 2.0
Statistics
Provide statistics interface
ResourceAdapter
ManagedConnectionFactory
Admin Object
Management
Provide management interface
ResourceAdapter
ManagedConnectionFactory
Admin Object
Metadata of which methods should be exposed
26. Java EE Connector Architecture 2.0
Conclusion
Simpler architecture – clear what to do
Easier to get started – only do what is needed
Use of modern approaches – do it easier
Most importantly
Java EE Connector Architecture 1.x maps on to Java EE Connector
Architecture 2.0
You will be able to deploy your old .rar archives
Developed under Java Community Process (JCP)
We value your feedback !
And get involved :)