Re: ResourceAdapterAssociation interface

I can't explain the ambiguity, but doing the instanceof check is how we
do it.

Jim Gish - BEA

-----Original Message-----
From: A public list for J2EE Connector architecture interest.
[mailto:[email protected]] On Behalf Of Hrishikesh Barua
Sent: Thursday, November 10, 2005 1:52 AM
To: [email protected]
Subject: ResourceAdapterAssociation interface

Hello,
  Ref : Connector Architecture Specification 1.5 Final Release Nov 2003
Section 5.3.2 ManagedConnectionFactory JavaBean and
OutboundCommunication:

  The spec mandates that the application server should call the
setResourceAdapter method on the ManagedConnectionFactory javabean. This
is
not possible without reflection as the
javax.resource.spi.ManagedConnectionFactory interface does not extend
the
ResourceAdapterAssociation, which has this method.
  Whereas in the similar case of the ActivationSpec the ActivationSpec
interface itself extends the RAA interface.
  Why this ambiguity? Is the application server supposed to check
whether
the MCF impl class implements the RAA interface by itself (using an
instanceof check)?


Regards
  Hrish

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D=3D=3D
To unsubscribe, send email to [email protected] and include in the
body
of the message "signoff CONNECTOR-INTEREST".  For general help, send
email to
[email protected] and include in the body of the message "help".

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff CONNECTOR-INTEREST".  For general help, send email to
[email protected] and include in the body of the message "help".