You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Thiago H de Paula Figueiredo <th...@gmail.com> on 2014/06/28 14:53:57 UTC
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-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Abandon java.beans.Introspector or keep working around it?
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
Nevermind, a not-too-ugly workaround was enough.
On Sat, 28 Jun 2014 09:53:57 -0300, Thiago H de Paula Figueiredo
<th...@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
> 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-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Abandon java.beans.Introspector or keep working around it?
Posted by Lance Java <la...@googlemail.com>.
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" <th...@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 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-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>