DriverAction implementation is not intended to be used
directly by applications. A JDBC Driver may choose
to create its
DriverAction implementation in a private class
to avoid it being called directly.
The JDBC driver's static initialization block must call
DriverManager.registerDriver(java.sql.Driver, java.sql.DriverAction) in order
DriverAction implementation to
call when the JDBC driver is de-registered.
Method SummaryModifier and TypeMethodDescription
voidMethod called by DriverManager.deregisterDriver(Driver) to notify the JDBC driver that it was de-registered.
deregistervoid deregister()Method called by DriverManager.deregisterDriver(Driver) to notify the JDBC driver that it was de-registered.
deregistermethod is intended only to be used by JDBC Drivers and not by applications. JDBC drivers are recommended to not implement
DriverActionin a public class. If there are active connections to the database at the time that the
deregistermethod is called, it is implementation specific as to whether the connections are closed or allowed to continue. Once this method is called, it is implementation specific as to whether the driver may limit the ability to create new connections to the database, invoke other
Drivermethods or throw a
SQLException. Consult your JDBC driver's documentation for additional information on its behavior.