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.

Bug 122440 - Default Custom SecurityManager should not be active for RCP.
Summary: Default Custom SecurityManager should not be active for RCP.
Status: NEW
Alias: None
Product: obsolete
Classification: Unclassified
Component: jini (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-20 22:23 UTC by greggwon
Modified: 2007-11-20 22:23 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description greggwon 2007-11-20 22:23:22 UTC 
The use of a custom Policy/SecurityManager makes it impossible to run Jini applications inside of the RCP which rely on
the security provided by the features of the normal SecurityManager.  There needs to be a plugable security manager
supported if the IDE really needs one.

The custom one that exists today, apparently is used to optimize file permission checks for speeding up those types of
things.  That's appropriate for the IDE, perhaps, but is not always useful for the RCP in general.