https://issues.apache.org/bugzilla/show_bug.cgi?id=55078
--- Comment #2 from Timothy Stewart <timothy.stew...@gmail.com> --- This problem isn't quite what I thought. I have some other issue than the one I described. The org.apache.tomcat.jdbc.pool.DataSourceFactory has code to resolve the DataSource from JNDI, and set it on the PoolConfiguration. It seems to work for most DataSources in my app, but not this one. I'm not sure whether to close this bug, or leave it open as a low priority. I feel the TODO could be resolved, and since the property is on the PooledConnection class configuration, other custom factories might not expect to do the JNDI lookup yourself. It is very minor at this point, but I think it would be safer for this class to do the resolution if it is not already resolved. Anyhow, if I find my original problem is a real Tomcat issue, I'll either comment here if related or open something else. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
