Re: Classloading issues...

Pat Niemeyer wrote:
> BeanShell currently has the notion of an externally supplied classloader,
> however there was a known bug causing it not to be used correctly.  That
> has been / should all be sorted out for the next release...
> 
> So, any externally supplied classloader will be used in preferenece to the
> rest and that functionality is what will be encapsulated by the bsh
> classloader, however it is exposed.

Excellent.

> On the topic of the sandbox, I do have a question there.  I know that
> access to the thread context classloader is priviledged.  Is it sufficient
> to simply try to access it and catch the SecurityException if we fail or
> do we have to find a way to completely shortcut that test?  I know that in
> the old days on some browsers when a security exception was thrown it
> brought things to a halt, regardless of how you tried to handle it.

I have never heard of this. I just did some google searches and found a 
bunch of links about folks who didn't catch the SecurityException and it 
_looked_ like their applet crashed when it was really their faulty 
Exception handling at work.

I'm not saying you're wrong, but I'm thinking that even if you are right 
it would have to be a bug from the _really_ old 1.[0,1] days and we can 
safely forget about it.

Cheers.

-- 
Free replacement for Exchange and Outlook (Contacts and Calendar)
http://www.ScheduleWorld.com/
WAP: http://www.ScheduleWorld.com/sw/WAPToday?id=4000&tz=EST
WebDAV: http://www.ScheduleWorld.com/sw/webDAVDir/4000.ics
VFREEBUSY: http://www.ScheduleWorld.com/sw/freebusy/4000.ifb


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click