[ http://issues.apache.org/jira/browse/DERBY-1001?page=comments#action_12441172 ] Daniel John Debrunner commented on DERBY-1001: ----------------------------------------------
I would say b) is the correct solution. Any call in derby that could result in a security manager check/exception needs to be in a privileged block. However, I don't understand your concern to b) when you say "since the files Derby needs to read may be anywhere". Could you explain more? Thanks. > Rewrite 'store/encryptionKey.sql' to a JUnit test > ------------------------------------------------- > > Key: DERBY-1001 > URL: http://issues.apache.org/jira/browse/DERBY-1001 > Project: Derby > Issue Type: Test > Components: Test > Affects Versions: 10.2.1.6 > Reporter: Kristian Waagan > Assigned To: Kristian Waagan > Priority: Minor > > This test has failed on Solaris10 for a long time, due to issues with the > default security provider on this OS. See DERBY-788 for details. > I consider rewriting this test as interresting because it allows us to see > how things can be done in "the JUnit way". > 1) Run test with multiple encryption algorithms with minimal test code > duplication. > 2) Special handling of exceptions for specific providers (PCKS11-Solaris). > The rewritten test might cause some discussion on how we want to handle the > issues mentioned above. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
