Now considering the applciation you have described it sounds like a stand alone desktop application. If it is, why are you using a connection pool? You only need a maximum of one connections.
Originally posted by Paul Sturrock:
One way would be to validate the login credentials when you get them (I'm not 100% sure why you wouldn't do this anyway - if you don't do this, why get them at all?). All you need to do is try to directly create a Connection with these credentials and catch the SQLException if one is thrown. You could parse the Exception to make sure it is a permissions exception, but since any SQLException when you create a connection amounts to the same thing (i.e. you can't connect) I'm not sure this matters.
Originally posted by Balaji Loganathan:
It is a not good way to use the user entered credentials for connecting to database directly. Of course you will get an error message after a long time bcos the class to get a connection to db.
Originally posted by Baris Dere:
How did you implement locking mechanism?
Your exam results will show up in the Certification database within 4 weeks after taking the essay at Prometric.
Originally posted by Werner Joerling:
... there is neither an exception, nor a popup, but changes aren't persistent ...
Originally posted by Morgan Bath:
NIO doesnt work?? Seemed to work just fine for me