ConnectionFactoryManagedImpl may try to use pool
------------------------------------------------
Key: OJB-54
URL: http://issues.apache.org/jira/browse/OJB-54
Project: OJB
Type: Bug
Versions: 1.0.x CVS
Environment: JBoss/HSQL
Reporter: Michael Lipp
When I configure ConnectionFactoryManagedImpl as connection factory, I expect
that my already managed connection (e.g. from JBoss) is used. However, as
ConnectionFactoryManagedImpl.lookupConnection calls
ConnectionFactoryAbstractImpl.lookupConnection this is not the case.
ConnectionFactoryAbstractImpl.llokupConnection doesn't care whether or not
called from ConnectionFactoryManagedImpl. Rather, its behaviour depends on
jcd.isDataSource() which in turn depends on a data source name being set (and
in my case subsequently causes an error because it wants a driver name for
creating a pool and the driver name is not given).
This is not what the "uninitiated" user expects. Especially in conjunction
with using JdbcMetadataUtils. I used this to fill my JCD, set connection
factory to ConnectionManagedImpl and, of course, expected everything to work
find. No mentioning anywhere that I have to specify a data source name!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
