Knut Anders Hatlen wrote:
OK, I think I see the problem now. It seems like if you connect to a database which has derby.connection.requireAuthentication=true using the embedded driver, Derby throws a NPE if the securityMechanism connection attribute is specified. Specifying the securityMechanism attribute for an embedded connection doesn't really make any sense, I think, since it says how to send passwords over a network connection, and the embedded driver doesn't use the network.
Mekes sense, thanks.
This means you will have to connect without securityMechanism when you connect from within Tomcat (with the embedded driver), and with securityMechanism when you connect from the external scripts (with the client driver).
Right.
Of course, you should have got an exception with a message explaining the problem, not a NPE.
Hmm, aren't unrecognised properties just silently ignored? Shouldn't this be the same?
-- Alan Burlison --
