JDBCVirtualUserTable and DB Connection Pools

[Hut Carspecken <hu...@sbcglobal.net>]

Noel,

Thank you for the suggestion about the <servernames> ....worked like a charm.    I have been looking at the JDBCVirtualUserTable mailet and saw how it used avalon.excalibur.datasource.DataSourceComponent.

I assume that the package handles connection pooling; however, you are still openning and closing every time an instance of the mailet it closed.  Though I looked at the package for several hours today, I think I am missing something.  Does this package prevent the costly action of creating a connection and then closing it?  Right now, it appears that I could JDBC directly form java.sql and still get the same result.  Of course, I must be far off base.

Thanks,

Hut

RE: JDBCVirtualUserTable and DB Connection Pools

["Noel J. Bergman" <no...@devtech.com>]

> I have been looking at the JDBCVirtualUserTable mailet and saw how
> it used avalon.excalibur.datasource.DataSourceComponent.

> I assume that the package handles connection pooling; however, you
> are still openning and closing every time an instance of the mailet
> it closed.

Connection pooling is transparent to an application.  You write your client
code as if you were talking directly to the JDBC driver.

There are plenty of resources on the web related to JDBC connection pooling,
including the JDBC specification.  You've some reading to do.  :-)

	--- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org