Re: Abandon java.beans.Introspector or keep working around it?
Nevermind, a not-too-ugly workaround was enough. On Sat, 28 Jun 2014 09:53:57 -0300, Thiago H de Paula Figueiredo 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 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 have examples. What do you guys think about ditching its use? Or do you think we should work around it? Meanwhile, I'm trying a workaround. Cheers! -- Thiago H. de Paula Figueiredo Tapestry, Java and Hibernate consultant and developer http://machina.com.br - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: Abandon java.beans.Introspector or keep working around it?
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" 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 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 have > examples. What do you guys think about ditching its use? Or do you think we > should work around it? > > Meanwhile, I'm trying a workaround. > > Cheers! > > -- > Thiago H. de Paula Figueiredo > Tapestry, Java and Hibernate consultant and developer > http://machina.com.br > > - > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org > >
Abandon java.beans.Introspector or keep working around it?
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 have examples. What do you guys think about ditching its use? Or do you think we should work around it? Meanwhile, I'm trying a workaround. Cheers! -- Thiago H. de Paula Figueiredo Tapestry, Java and Hibernate consultant and developer http://machina.com.br - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
