-
Enhancement
-
Resolution: Won't Fix
-
P5
-
None
-
1.2.0, 1.4.0
-
generic, x86
-
generic, windows_2000
Name: krT82822 Date: 02/09/99
original synopsis: Order of Fields from "Class.getFields()" in "no particular order".
The documentation for "Class.getFields()" states that it returns
the Fields in "no particular order". This is very inconvenient.
In order to write a "stable" Object-Relational mapper, I have to
have a guarantee that the call to "Class.getFields()" will return
the Fields in the same order each time, assuming the Class hasn't
changed. Once the Class changes, I don't need any guarantee.
If I don't have that guarantee, then I'll have to sort the Fields
each time I get them. That will make it much slower.
(Review ID: 48184)
======================================================================
original synopsis: Order of Fields from "Class.getFields()" in "no particular order".
The documentation for "Class.getFields()" states that it returns
the Fields in "no particular order". This is very inconvenient.
In order to write a "stable" Object-Relational mapper, I have to
have a guarantee that the call to "Class.getFields()" will return
the Fields in the same order each time, assuming the Class hasn't
changed. Once the Class changes, I don't need any guarantee.
If I don't have that guarantee, then I'll have to sort the Fields
each time I get them. That will make it much slower.
(Review ID: 48184)
======================================================================
- relates to
-
JDK-4773520 (reflect) Class.getFields() returns data differently in 1.3 and 1.4
- Closed