AccessibleObject redundant check

[Bryce McKinlay]

Anyone care to comment on this patch? Checking for whether we are 
setting accessibility on a member of AccessibleObject seems redundant, 
as code can only do that if it has already passed the SecurityManager 
check required to call setAccessible() in the first place (the check 
for java.lang.Class constructors, however, is specified by Sun's docs 
so we should probably keep that one).

Regards

Bryce.

AccessibleObject.patch.txt
Description: Text document