More info:
It turns out that after testing with two different connection pools, the
underlying problem is a java.sql.SQLException ("No suitable driver").
This only shows up for the second test class. The first one gets a connection
just fine and my tests pass.
I still vote for the container per suite option, but if someone has any tips on
dealing with this short term issue I'm having that would be great.
Why is the driver class not found for the second test? How does the TestNG
suite classpath work? My driver is definitely on the classpath of my Eclipse
projects.
In addition, I tried classloading the JDBC driver explicitly before each test
method, but to no avail.
Any thoughts on what could be causing this?
Thanks
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4021840#4021840
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4021840
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
