I am not sure if this is a bug, or that the usage of DataSourceComponent/JdbcConnection has changed.
Have existing code like: DataSourceComponent myDataSourceComponent = ......get a ResourceLimitingJdbcDataSource ..... Connection myConnection = myDataSourceComponent.getConnection(); But, getting a ClassCastException in ResourceLimitingJdbcDataSource.getConnection() on the return statement where "(Connection)connection" cast is done. "connection" (Object) is a JdbcConnection, extends AbstractJdbcConnection, neither of which implement Connection any longer. Looks like these have been changed to use proxies. Question is what should I change to adapt? Thanks, Shash ----- Original Message ----- From: "Berin Loritsch" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, March 24, 2003 2:57 PM Subject: Excalibur Phase II Release Candidate 1 > I have assembled the next eight products/projects for > Excalibur release. They can be accessed at the following > location: > > http://avalon.apache.org/~bloritsch/excalibur-dist/ > > The collection of projects are: > > Compatibility > Configuration > DataSource > Event > Monitor > SourceResolve > Thread > ThreadContext > > > These eight should be pretty straight-forward. > Please send in all your comments so that we can get > the changes folded in ASAP. I would like to go through > as few iterations as possible, so please send in as > many comments as possible so that we can address them > quicker. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
