Message711

In presence of an overloaded setter,e.g.

void JLabel.setDisplayedMnemonic(char)
void JLabel.setDisplayedMnemonic(int)
int JLabel.getDisplayedMnemonic()

only the int type is considered for the property.

Maybe it is OK so, but this deserve further
thinking.

Also if I recall correctly a past exploration of the code, 
the whole process
of disovering properties is not completely
deterministic (depends on the order of the result from 
the java reflection methods) in some corner case.
True/false? to recheck.

Finally

respectJavaAccessibility = false

gives access to protected and private fields,
and the fields take over the potential corresponding
properties, this is bad because it means
that code have different behaviour depending
on respectJavaAccessibility, that means
code using the prop shortcuts will now
access the fields directly and needed
side-efffect would be lost.

When fields clash with a property, they
should be made visible but somehow renamed.
Yes, this is backward incompatible, but
nobody in their right mind should have
production code depending on

respectJavaAccessibility = false

On the other hand for Jython development
tools written in Jython using the  prop shortcuts
for expressivity to still work with

respectJavaAccessibility = false

is important (I have been bitten by this
with my old jppad).