[ http://issues.apache.org/jira/browse/DERBY-871?page=comments#action_12364419 ]
Daniel John Debrunner commented on DERBY-871: --------------------------------------------- Thanks Kathey, leads to three new questions: 1) How are the new properties csinfo.server and csinfo.client different to cs.serverhost and cs.trustedhost? 2) Why is csinfo.trustedhost granted 'connect' permission for derbynet.jar in the testing policy file? The server isn't connectiing to the client is it? 3) Would csinfo.clienthost be a better name for csinfo.trustedhost? Not sure exactly what you are asking of me for property cleanup in DERBY-871, but I think a start is a clear definition of any properties used in the testing policy file. It's possible that the remote testing (even using useProcess=false) does not need any changes to the policy file or the harness. > remote host support in test harness needs more work because of security > manager changes > --------------------------------------------------------------------------------------- > > Key: DERBY-871 > URL: http://issues.apache.org/jira/browse/DERBY-871 > Project: Derby > Type: Bug > Components: Test > Versions: 10.2.0.0 > Reporter: Myrna van Lunteren > Assignee: Myrna van Lunteren > Priority: Minor > Attachments: DERBY-874-012906.diff, DERBY-874-012906.stat > > With the changes to have security manager run for tests with > useprocess=false, the remote host support in the test harness no l onger > works. > permissions need to be passed in derby_test.policy for the client. -- 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
