|
Quick Lists
|
|
Bug ID:
|
6558953
|
|
Votes
|
0
|
|
Synopsis
|
(cl) assign correct ProtectionDomain
|
|
Category
|
java:module
|
|
Reported Against
|
|
|
Release Fixed
|
7(beta)
|
|
State
|
10-Fix Delivered,
request for enhancement
|
|
Priority:
|
4-Low
|
|
Related Bugs
|
|
|
Submit Date
|
17-MAY-2007
|
|
Description
|
The ClassLoader does not assign the correct ProtectionDomain to loaded code. This needs to be fixed.
Posted Date : 2007-05-17 19:12:46.0
|
|
Work Around
|
N/A
|
|
Evaluation
|
The current implementation has assigned ProtectionDomain based on CodeSource, and CodeSource is constructed from a module URL and an array of CodeSigner obtained from ModuleDefinitionContent. Unclear if there is anything more needs to be done.
Posted Date : 2007-09-21 00:59:01.0
This is fixed as part of the repository implementation refactoring.
Posted Date : 2008-04-03 01:11:43.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
