Abandon java.beans.Introspector or keep working around it?

2014-06-28 Thread Thiago H de Paula Figueiredo
Hi! While investigating TAP5-1548 and TAP5-1885 and also reading TAP5-921 I reached the conclusion that Introspector isn't finding all the properties in some circustances, specially when the getter is defined in one type and the setter in another one in the class hierarchy. The tickets

Re: Abandon java.beans.Introspector or keep working around it?

2014-06-28 Thread Lance Java
Yeah, I must say I thinking the same thing. It's not rocket science what the introspector is doing. We could support isX() for java.lang.Boolean too if we had our own introspector. On 28 Jun 2014 13:54, Thiago H de Paula Figueiredo thiag...@gmail.com wrote: Hi! While investigating TAP5-1548

Re: Abandon java.beans.Introspector or keep working around it?

2014-06-28 Thread Thiago H de Paula Figueiredo
Nevermind, a not-too-ugly workaround was enough. On Sat, 28 Jun 2014 09:53:57 -0300, Thiago H de Paula Figueiredo thiag...@gmail.com wrote: Hi! While investigating TAP5-1548 and TAP5-1885 and also reading TAP5-921 I reached the conclusion that Introspector isn't finding all the