Re: ResourceAdapter and MCF instances

With version 1.5 of the connector architecture you
can define several connection types in a single resource
adapter. So you don't need a single RA for each connection
type. Having 2 RAs allows you to make each connection type
available independently of each other; other than that I don't
see any other reason to do that, since both RAs will be
sharing several classes.

A deployment descriptor for a RA with multiple connection type
looks like this:

<resourceadapter>

         <resourceadapter-class>RA Class</resourceadapter-class>

         <outbound-resourceadapter>

             <connection-definition>
                detail for Connection type 1 (MCF, MC, props, etc)
            </connection-definition>
            <connection-definition>
                detail for connection type 2 (MCF, MC, props, etc)
            </connection-definition>


        </outbound-resourceadapter>
....
</resourceadapter>

So you'll  need to define the set of properties in both connection
definitions.

Alejandro



Jeff Crump wrote:

> I'm porting my resource adapter to J2CA 1.5 and I'm wondering about the
> relationship between the ResourceAdapter class and its MCF instances.
>
> The EIS I'm connecting to has both "remote" (over the network) and "local"
> (inproc) connection types; my J2CA 1.0 implementation has an MCF
> implementation for each.  The two implementations share a base class and a
> small set of properties.
>
> In 1.5, should I have two different ResourceAdapter classes, or would one
> suffice?  What are the pros/cons of selecting one approach over the other?
>
>
> -----------------------
> Jeff Crump
> Sonic Software Corporation
> Sr. Software Engineer, XIS
> [email protected]
> tel: +1 781 999 7030
> http://www.sonicsoftware.com
>
> ===========================================================================
> 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".
>


--
Alejandro E. Murillo
Java (tm) Partner Engineering, Sun Microsystems, Inc

===========================================================================
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".