By jagadish on Dec 02, 2009
Java EE Connector Architecture 1.6 Reference Implementation :
Connector 1.6 Specification is approved now ! Also refer the announcement by Siva. GlassFish v3 is the reference implementation of this version of the specification.
Developers can write resource-adapters leveraging the new features introduced in this specification and deploy the resource-adapters in
GlassFish v3. GlassFish v3 builds are available now !
Major features of Connector 1.6 specification available in GlassFish v3 :
Ease of Use : Annotation
- It is now possible to develop a resource-adapter using various annotations defined in Connector 1.6, without deployement descriptor (ra.xml)
- Refer the blog
made available during GlassFish v3 Preview SDK release
Generic and Standard Work Context Mechanism
- Generic work context contract enables a resource adapter to control the contexts in which the work instances submitted by it are executed by the application server's WorkManager.
- Connector 1.6 mandates the following Work Context mechanisms to be supported by all application servers
- Transaction Context (Similar to existing ExecutionContext)
- Security Context
- Hints Context
Bean Validation support for resource-adapters
- With Bean Validation mechanisms made available in Java EE 6 specification, Connector 1.6 allows resource-adapters to use Bean Validation mechanisms to validate various resource-adapter artifacts ie., ResourceAdapter, AdministeredObject, ManagedConnectionFactory, ActivationSpec JavaBeans.
- Connector 1.6 specification recommends that the availability of
resource-adapters to applications should be based on the reference of
resource-adapter in the application's deployment-descriptor (or its
equivalent annotations). These references can be via resource-ref (connector-resource), resource-env-ref (administered-object), resource-adapter-mid (for inbound).
By default, GlassFish v3 supports the above recommendation.
Runtime Transaction Support
- With the introduction of javax.resource.spi.TransactionSupport,
a ManagedConnectionFactory artifact can dynamically request a
transaction support level (XA/Local/NoTransaction) at runtime to
override the value specified via deployment-descriptor (or its
In the coming weeks, you can look forward for more articles, tutorials, blogs on these features.