12.11.2014 Views

web server - Borland Technical Publications

web server - Borland Technical Publications

web server - Borland Technical Publications

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Developing the Resource Adapter<br />

tracing, and security management. The default ConnectionManager delegates to the<br />

ManagedConnectionFactory the creation of physical connections to the underlying EIS.<br />

In an application-<strong>server</strong>-managed environment, the Resource Adapter should not use<br />

the default ConnectionManager implementation class. Managed environments do not<br />

allow resource adapters to support their own connection pooling. In this case, the<br />

application <strong>server</strong> is responsible for connection pooling. A Resource Adapter can,<br />

however, have multiple ConnectionManager instances per physical connection<br />

transparent to the application <strong>server</strong> and its components.<br />

Transaction management<br />

Resource Adapters are easily classified based on the level of transaction support they<br />

provide. These levels are:<br />

■<br />

■<br />

NoTransaction: the Resource Adapter supports neither local not JTA transactions,<br />

and implements no transaction interfaces.<br />

LocalTransaction: the Resource Adapter supports resource manager local<br />

transactions by implementing the LocalTransaction interface. The local transaction<br />

management contract is specified in Section 6.7 of the Connectors 1.0 specification<br />

from Sun Microsystems.<br />

■<br />

XATransaction: the Resource Adapter supports both resource manager local and<br />

JTA/XA transactions by implementing the LocalTransaction and XAResource<br />

interfaces, respectively. The XA Resource-based contract is specified in Section 6.6<br />

of the Connectors 1.0 specification from Sun Microsystems.<br />

The transaction support levels above reflect the major steps of transaction support that<br />

a Resource Adapter must implement to allow <strong>server</strong>-managed transaction<br />

coordination. Depending on its transaction capabilities and the requirements of its<br />

underlying EIS, a Resource Adapter can choose to support any one of the above<br />

levels.<br />

Security management<br />

The security management contract requirements for a Resource Adapter are as<br />

follows:<br />

■<br />

■<br />

■<br />

The Resource Adapter is required to support the security contract by implementing<br />

the ManagedConnectionFactory.createManagedConnection() method.<br />

The Resource Adapter is not required to support re-authentication as part of its<br />

ManagedConnection.getConnection() method implementation.<br />

The Resource Adapter is required to specify its support for the security contract as<br />

part of its deployment descriptor. The relevant deployment descriptor elements are:<br />

■<br />

<br />

■<br />

<br />

■<br />

<br />

■<br />

<br />

Refer to section 10.3.1 of the Connectors 1.0 specification for more details on these<br />

descriptor elements.<br />

Chapter 27: Using VisiConnect 269

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!