On 5/27/2016 7:03 PM, Sergey Bylokhov wrote:
On 27.05.16 18:06, Semyon Sadetsky wrote:
Sergey, what do you think, may this misunderstanding be caused by the
bug title: "Unstable behavior of PropertyDescriptor's getWriteMethod()
in case of overloaded setters" ? And, of cause, by the test mentioned in
the bug summary, and the test proposed in your fix, which examines the
Introspector. getPropertyDescriptors(), not the Class.getMethods()?
Did you think I should change behavior of "Class.getMethods()" and use
it in the test directly?
Well it depends on the bug purpose.
(1)If the goal is to fix the Introspector.getPropertyDescriptors()
overloaded setters, then the test is OK, but I don't agree with the
solution.
(2)If the goal is to have Class.getMethods() stably returning the same
order of methods regardless of JVM or the machine it runs, then the test
is not OK, but the solution is good. (In my understanding of cause)
From the bug description and the test I thought that the purpose is (1).
