sebb wrote:
Having a ready-made test app might encourage others to test as well.
What do you have in mind here? An "OracleTestApp" class checked into our tests? Or an "IntegrationTestApp" that would work against multiple vendors?
I can certainly imagine an OracleTestApp, but naturally I'm not in a good position to write it since I don't actually have Oracle. (Also, would we have to add the Oracle JDBC driver to our POM?)
The problem gets even more complicated if we tried to write a generic "IntegrationTestApp" to work against multiple venders. How would the IntegrationTestApp know what column types are possible? How would it manage access to the DataSource in a vendor-agnostic way? Would we have to add a dozen (closed source?) DB drivers to our test classpath?
-Dan --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
