14.3.3. Access Vendor Specific Classes
Summary
This topic covers the steps required to use the JDBC specific classes. This is necessary when an application uses a vendor specific functionality that is not part of the JDBC API.
Warning
This is advanced usage. Only applications that need functionality not found in the JDBC API should implement this procedure.
Important
This process is required when using the reauthentication mechanism, and accessing vendor specific classes.
Important
Follow the vendor specific API guidelines closely, as the connection is being controlled by the IronJacamar container.
Prerequisites
Procedure 14.2. Add a Dependency to the Application
Configure the
MANIFEST.MFfile- Open the application's
META-INF/MANIFEST.MFfile in a text editor. - Add a dependency for the JDBC module and save the file.
Dependencies: MODULE_NAME
Example 14.2. Example Dependency
Dependencies: com.mysql
Create a
jboss-deployment-structure.xmlfileCreate a file calledjboss-deployment-structure.xmlin theMETA-INF/orWEB-INFfolder of the application.Example 14.3. Example
jboss-deployment-structure.xmlfile<jboss-deployment-structure> <deployment> <dependencies> <module name="com.mysql" /> </dependencies> </deployment> </jboss-deployment-structure>
Example 14.4. Access the Vendor Specific API
The example below accesses the MySQL API.
import java.sql.Connection; import org.jboss.jca.adapters.jdbc.WrappedConnection; Connection c = ds.getConnection(); WrappedConnection wc = (WrappedConnection)c; com.mysql.jdbc.Connection mc = wc.getUnderlyingConnection();
