I think that maybe this is a testsuite error and not a jboss one ... - I do it in *cascades* - this might exhibit problem ? ... because some testsuites as of now leaves "crack" behind --not dropping tables and keep simulated corporate data - then in existence on the next run ---SLOPPY ... I have a fix where We would employ a SQLCache for the tests suite either called throughout a DataSource or direct to a hsqldb connection ... the thing is to always call YOUR JDBC THROUGH A DS WHEN IN TESTSUITE ... otherwise We will <blow> inconsistently ... happens now with my *new* test in jmx.test !!! please fix so I can employ fix without breaking Your test/s !.
Thanks /peter_f _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
