X-Mozilla-Keys:                                                                                 
Message-ID: <4BB4438E.2030901@Sun.COM>
Date: Thu, 01 Apr 2010 12:26:14 +0530
From: Sivakumar Thyagarajan <Sivakumar.Thyagarajan@Sun.COM>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: Java Community Process JSR #322 Expert List <JSR-322-EG@JCP.ORG>
Subject: Errata in Section 18.7 of the Connector 1.6 spec -- Implementing
 ActivationSpec interface
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi everyone

Wilson Tian brought to our notice an error in the Connectors 1.6 final 
spec.

As part of the EoD related changes, the spec had made it optional(in
Section 18.7) for an ActivationSpec JavaBean to implement the 
javax.resource.spi.ActivationSpec interface. However this prevents such 
a JavaBean to be provided by the application server during endpoint 
activation/deactivation/transaction recovery as the ResourceAdapter 
interface requires the activation spec to be an instance of the 
ActivationSpec interface.

ResourceAdapter.endpointActivation(MessageEndpointFactory 
endpointFactory, ActivationSpec spec) [1]

To fix this, we need to remove this option in 18.7 and make it mandatory 
for an ActivationSpec JavaBean that is annotated with the @Activation 
annotation. As a clarification, An @Activation JavaBean after this 
change, like all other JavaBeans listed in Section 5.3.7.5, can have 
Bean Validation annotations placed on them.

I learnt that the only way to make errata available to the public is 
through a maintenance release (MR), but that can only happen after we 
have a sizable list of changes. We will continue accumulating a list of 
"pending" or "proposed" errata to the spec, that will become "accepted" 
after the MR.

Thanks
--Siva.
[1] 
http://java.sun.com/javaee/6/docs/api/javax/resource/spi/ResourceAdapter.html#endpointActivation(javax.resource.spi.endpoint.MessageEndpointFactory,%20javax.resource.spi.ActivationSpec)