I think this issue is going to go away when we change to only use the CpoAdapter for the datasource as CpoUtil will no longer be loading the driver class at all...the api would.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We currently do it the other way. We try to load it off the classpath, if it can't be found or has issues, we attempt to load it off the custom classpath.
I can reverse this order, though I'm not sure why it was done this way...probably to look if it wasn't there, but I like the overloading thing.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think this issue is going to go away when we change to only use the CpoAdapter for the datasource as CpoUtil will no longer be loading the driver class at all...the api would.
We currently do it the other way. We try to load it off the classpath, if it can't be found or has issues, we attempt to load it off the custom classpath.
I can reverse this order, though I'm not sure why it was done this way...probably to look if it wasn't there, but I like the overloading thing.