<AWT Dev> [8] Review request for 7117595: ArrayIndexOutOfBoundsException in Win32GraphicsEnvironment if display is removed

[Sergey Bylokhov]

On 23.09.2013 17:45, Anthony Petrov wrote:
> That indeed seems logical. Moreover, the HeadlessException doesn't 
> have a specification yet (see 8016313). However, I think that AWT 
> doesn't consider itself headless even if the devices array is empty. 
> Headless is a special mode, after all. I'd go with returning null for 
> now - other code will catch NPEs, but that's OK. Later we may decide 
> whether consider this case headless or not.
I think that we should not return null here, but instead we should 
somehow handle situations then list of screens is updated to the empty 
array not then it used.
>
> -- 
> best regards,
> Anthony
>
>>
>>> -- 
>>> best regards,
>>> Anthony
>>>
>>> On 09/23/13 16:47, sergey malenkov wrote:
>>>> Hello,
>>>>
>>>> Could you please review the following fix:
>>>> fix:http://cr.openjdk.java.net/~malenkov/7117595.8.0/
>>>> bug:https://bugs.openjdk.java.net/browse/JDK-7117595
>>>>
>>>> Thanks,
>>>> SAM
>>


-- 
Best regards, Sergey.