|
Quick Lists
|
|
Bug ID:
|
6573885
|
|
Votes
|
0
|
|
Synopsis
|
(modinit) Incorrect recursion check in module initialization
|
|
Category
|
java:module
|
|
Reported Against
|
|
|
Release Fixed
|
7(beta)
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
3-Medium
|
|
Related Bugs
|
|
|
Submit Date
|
26-JUN-2007
|
|
Description
|
The module initialization algorithm contains code dealing with cases such as the custom import policy for module M requesting module M itself. This currently works correctly more by accident then by design because an explicit check is missing but the reference causes an AssertionError later on than also has the effect of moving M into error state. This should be fixed by adding the correct check.
Posted Date : 2007-06-26 09:14:47.0
|
|
Work Around
|
N/A
|
|
Evaluation
|
The module initialization logic should check if the module definition to be instantiated is the same module definition of the initializing module instance. See mtest/importpolicy/recurse2.mtest.
Posted Date : 2008-07-29 21:01:35.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |