[Fwd: Re: How can I get sysinfo for a custom Derby classloader?]

[Bryan Pendleton <bp...@amberpoint.com>]

 > The work that I did on classloaders (but have not yet committed) could
 > help with this.  If somebody has an itch to work on this I can show them
 > what I did and why I think it will work.

Yes, I'm definitely interested in learning more about this.

I picked up some code that was floating around on the derby-dev list
a few weeks back that basically did

   cls.getProtectionDomain().getCodeSource().getLocation().toString();

I think maybe Rick was using this code in one of his patches.

Is this the technique that you mean, David?

thanks,

bryan

Re: [Fwd: Re: How can I get sysinfo for a custom Derby classloader?]

["David W. Van Couvering" <Da...@Sun.COM>]

Yep, this is it, Bryan, I sent that code to Rick.  Sounds like you're on 
your way.  I'm glad to see this happening -- I knew we could use it for 
sysinfo but never got around to implementing it.

Look out for SecurityManager issues, however, 
getProtectionDomain().getCodeSource() is a restricted operation...

David

Bryan Pendleton wrote:
>  > The work that I did on classloaders (but have not yet committed) could
>  > help with this.  If somebody has an itch to work on this I can show them
>  > what I did and why I think it will work.
> 
> Yes, I'm definitely interested in learning more about this.
> 
> I picked up some code that was floating around on the derby-dev list
> a few weeks back that basically did
> 
>   cls.getProtectionDomain().getCodeSource().getLocation().toString();
> 
> I think maybe Rick was using this code in one of his patches.
> 
> Is this the technique that you mean, David?
> 
> thanks,
> 
> bryan
> 
> 
>