Thanks everyone, I made it! Maybe it was a classpath conflict, because I specifyed more than once the path to get the derby.jar file. I removed every call to -classpath, then I used it only in the activatable server setup, and it works :) probably as kristian said there were a mess with that.
Thanks again -- View this message in context: http://old.nabble.com/Derby-%3A-No-suitable-driver-found-for-jdbc%3Aderby%3Adb-create%3Dtrue-tp30335341p30366664.html Sent from the Apache Derby Users mailing list archive at Nabble.com.
