This question concerns the environment of your Java Application.
You call Connection.close(). This returns the connetion to the pool and doesn't close the real connection.
The default pool manager is a static instance. It maps the connections to all program parts in one JVM.
If you call:
PoolManager.getDefault(); you receive the defaut instance of the pool manager i-net PLEXA . This instance is using from the pooled driver. You can config the pool manager with its API now.
The pooled driver (subprotocol inetpool) uses
com.inet.pool.PoolManager.getDefault(); internally. If you request this instance of the PoolManager i-net PLEXA? you can control the pooled driver via the API of the PoolManager.
No, i-net PLEXA comes with i-net OPTA, i-net SEROPTO and i-net MERLIA. i-net PLEXA cannot be purchased separately.
There are no major differences like performance or feature. The used API is in general a matter of taste. Both solutions are for a standalone application. In an application server you should use the feature of the application server.
|pooled driver||i-net PLEXA|
|-||The driver creates a new ConnectionPoolDataSource every time||+||You can create a static global ConnectionPoolDataSource.|
|+||You can use it with an existing Application. You only need to change the JDBC URL.||-||In an existing application you need to change the getConnection() calls.|
|-||If you use another driver (other than i-net software) then you must register both drivers.||+||The ConnectionPoolDataSource of the driver registeres the needed drivers automatically. You do not need to register any drivers.|
|-||You only use one instance of i-net PLEXA (default instance). (This does not mean not multiple pools)||+||You can create multiple instances of i-net PLEXA. (This does not mean multiple pools)|
|+||You can remove the pooling very simple. You only need to change the JDBC URL.||-||You must modify your program. For example to change to a non pooled DataSource.|