Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <440783A5.5050705@apache.org>
Date: Thu, 02 Mar 2006 15:45:41 -0800
From: Daniel John Debrunner <djd@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.7.3) Gecko/20040910
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: Security manager problems with Class.forName()
References: <440733FE.1020408@Sun.com> <440736C1.1090206@sun.com>
 <44076879.1090306@Sun.COM> <44077D1B.6010708@sun.com>
In-Reply-To: <44077D1B.6010708@sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Rick Hillegas wrote:

> Hi Kristian,
> 
> ...
> 
>>
>> I just looked at the patch quickly, and it solves the problem in the
>> same way I was thinking about. I will try it out. Any specific reason
>> why the patch is not attached to DERBY-623 in Jira?
> 
> 
> Two lazy reasons: 1) The JIRA itself doesn't have a test case. The
> problem only comes up in the context of other JIRAs where you are
> creating a new test. 

That's not the case, removing the permissions added for DERBY-623
described in the description and in the testing policy file will
demonstrate the issue.

from derby_tests.policy

  // BUG DERBY-623 - sane=true
  permission java.util.PropertyPermission "derby.monitor.verbose", "read";
  permission java.util.PropertyPermission "derby.debug.*", "read";

I'll add a comment to the Jira entry to be clear.

Dan.