|
Quick Lists
|
|
Bug ID:
|
4759974
|
|
Votes
|
0
|
|
Synopsis
|
Field WindowEvent.opposite should be transient
|
|
Category
|
java:classes_awt
|
|
Reported Against
|
1.4
|
|
Release Fixed
|
1.4.2(mantis)
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
4-Low
|
|
Related Bugs
|
4715486
|
|
Submit Date
|
08-OCT-2002
|
|
Description
|
Since the source field on event object is transient, it is very unlikely that
someone can deduce anything useful from opposite field. Deserialized window
could have never actually be activated or receive focus. So null seems to be
the only possible value for WindowEvent.opposite field after deserialization.
There was a similar issue with FocusEvent.opposite reported by a customer from
HP (see bug id 4715486). This was resolved by making the field explicitly
serialize and deserialize to null. Michael Warres pointed out that since the
observable behaviour in this case is the same as if the field was transient, we
can as well make it transient. So I believe the issue of 4715486 needs to be
revisited and both WindowEvent.opposite and FocusEvent.opposite must be
transient.
|
|
Work Around
|
N/A
|
|
Evaluation
|
If we decided to change FocusEvent, WindowEvent needs to be changed, too.
xxxxx@xxxxx 2002-10-08
|
|
Comments
|
Submitted On 15-DEC-2005
vuistvechter1
waarom
Submitted On 15-DEC-2005
vuistvechter1
jan moorlag geluksdog1@hotmail.com
Submitted On 15-DEC-2005
vuistvechter1
wat kan ik daar aan doen
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
