Anonymous | Login | Signup for a new account | 12-17-2024 12:02 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0001932 | [Resin] | minor | always | 08-07-07 08:56 | 11-05-07 14:55 | ||||
Reporter | ferg | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | Platform | |||||
Status | closed | OS | |||||||
Projection | none | OS Version | |||||||
ETA | none | Fixed in Version | 3.1.4 | Product Version | |||||
Product Build | |||||||||
Summary | 0001932: DataSource casting | ||||||||
Description |
(rep by Geoff Hendry) I've got an interesting database pooling need. I have multiple databases, each with a different URL which is determined dynamically at runtime. Therefore, I cannot provide these URL (or associated database info) at configuration time. I need to be able to dynamically instruct Derby's DataSource to provide a connection to a particular database, with particular parameters. On Jetty web server, I cast the DataSource to a org.apache.derby.jdbc.ClientConnectionPoolDataSource and I can then call methods on that class to point it at the right database. However, on resin, the DataSource returned to me is the DBPool. What I need is some way to get at the underlying ClientConnectionPoolDataSource and call methods on it. I was looking at the JDK 6/JDBC 4 Wrapper class as a possible way to get at the underlying DataSource implementation, but I don't kow if that's the rght aproach, or if Resin even supports it. If I use a standard non-pooled org.apache.derby.jdbc.ClientDataSource then I don't have this problem since Resin just returns the ClientDataSource as expected. But then I don't get pooling, which I need. Please advise. |
||||||||
Steps To Reproduce | |||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed. 25 unique queries executed. |