web server - Borland Technical Publications

Other Considerations
}
}
{
cf = new GoodConnectionFactory( refMcf, refCm );
}
else
{
cf = new GoodConnectionFactory( refMcf );
}
return cf;
}
return null;
Update the classes in the ra.xml standard deployment descriptor file. For example,
before extending the implementation, the ra.xml may look something like this:
com.shme.shmeAdapter.
LocalTxManagedConnectionFactory
javax.sql.DataSource
com.shme.shmeAdapter.BadConnnectionFactory
java.sql.Connection
com.shme.Connection
After extending the interfaces, the ra.xml may look something like this:
com.shme.shmeAdapter.
LocalTxManagedConnectionFactory
javax.sql.DataSource
com.shme.shmeAdapter.GoodConnectionFactory
java.sql.Connection
com.shme.shmeAdapter.Connection
As this illustrates, this conversion only impacts the connection factory. No other
Resource Adapter classes are affected by this conversion.
Compile the Java code for the extended implementation (and any helper classes) into
class files.
Package these into the Resource Adapter's Java Archive (.jar) file.
Update the Resource Adapter Archive (.rar) file with this extended .jar.
Deploy the Resource Adapter Archive, or include it in an Enterprise Application Archive
(.ear) file to be deployed as part of a J2EE application, to VisiConnect running
standalone or as a Partition service in the Borland Enterprise Server.
You've now converted a badly behaving Resource Adapter into a well behaving one.
Sometimes the design of a Resource Adapter makes it impossible to extend the
existing API implementation. In such cases you need to re-implement the offending
class or classes, and set the elements in ra.xml to reference the re-implementation(s).
Or better yet, choose another Resource Adapter, which is compliant with the
Connectors specification to work with.
282 BES Developer’s Guide