db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmarsdende...@sbcglobal.net>
Subject Re: [jira] Commented: (DERBY-1273) Sysinfo should print a better message when it gets Security Exceptions accessing classpath info when run under security manager
Date Fri, 05 May 2006 17:04:52 GMT
Bryan Pendleton (JIRA) wrote:

>I think that the current statement of things is something like:
> - getProtectionDomain is a useful call, but it requires too many permissions under a
SecurityManager, so for the purposes of SysInfo, which merely wants to report on the actual
location from which an already-loaded class was loaded, we feel that getResource is a superior
>How does that sound?
I think it is really great that we are getting rid of  the 
getProtectionDomain permission requirement for sysinfo especially if 
DERBY-1272 is implemented as I hope it will be.    If  DERBY-1272 is 
implemented sysinfo will be used often in embedded security manager 
environments and in custom class-loaders where the classpath might have 
a different location than that of the jar being used.

What exactly do we lose by using getResource instead of 
getProtectionDomain?  Might sysinfo ever print a wrong location?


View raw message