This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Access permission error when customizing a bean | ||
---|---|---|---|
Product: | platform | Reporter: | Jesse Glick <jglick> |
Component: | Nodes | Assignee: | David Strupl <dstrupl> |
Status: | CLOSED FIXED | ||
Severity: | blocker | CC: | pkuzel |
Priority: | P2 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Log file |
Description
Jesse Glick
2001-11-30 14:08:12 UTC
Created attachment 3641 [details]
Log file
What about try { // invoking the method without setting accessible } catch (IllegalAccessException ex) { AccessController.invokePrivileged( {... method.setAccessible(true); method.invoke(..); .. } } Again it is just a hack of JDK bug. Will try Jesse's suggestion and if it works well will integrate on Monday. PropertySupport 1.13.18.1 (release33 branch). Please note that I have used suggestions from both of you. First I added setAccessible only if regular invocation fails. Second I am not calling the invoke method from under doPrivileged and thus I am not creating any security hole. Could you guys make a code review for me to get this fix into release330? Thanks a lot for a prompt reply. Making 3.3.0 candidate. Please note that there can be other security exceptions when using customize bean - for example when the bean is a java.awt.Window. But those should probably be filed separately. Verified in build#200112040330 (release33). Fixed in release330. Target milestone 3.3. Resolved for 3.4.x or earlier, no new info since then -> closing. |