Created attachment 228556 [details] [diff] [review] Potential fix? I had made a mistake in my earlier post, if there is a get function and no set function, it did function correctly (I simply had written my get function in Foo.java incorrectly!). However, the original problem (a set method but no get method) still applies. This patch fixes the problem for me.
Reviewed and committed the fix - will be in 1.6R3
(In reply to comment #3) > Reviewed and committed the fix - will be in 1.6R3 > Now I'm experiencing a similar problem on 1.6R3! Now, when you have both the setter and the getter, the property is not added to the members. Stepping through the reflect() method, it seems that when the iteration encounters a getter, it registers the property with the "toAdd" map, but then, when it encounters the setter, it overrides it with a BeanProperty that holds a null getter.
Created attachment 233039 [details] [diff] [review] Patch to fix the bean property regression This patch should fix the problem in JavaMembers that results in some bean properties not being exposed properly in NativeJavaObjects.
Ok, I commited your fix to CVS HEAD - actually refactored it a bit, as there was some code duplication in there (for looking up both getXxx and isXxx), other than that I didn't change it. Thank you again, and give it a try sometime.