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
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
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
See https://builds.apache.org/job/tapestry-trunk-freestyle/1261/changes
Changes:
[thiagohp] TAP5-1885: Error in PropertyAccess service
--
[...truncated 25365 lines...]
0 nanoseconds spent performing 0 L2C puts;
0 nanoseconds spent performing 0 L2C
See https://builds.apache.org/job/tapestry-trunk-freestyle/1262/changes
Changes:
[thiagohp] Added test for TAP5-1480.
--
[...truncated 25372 lines...]
0 nanoseconds spent performing 0 L2C puts;
0 nanoseconds spent performing 0 L2C hits;
0
See https://builds.apache.org/job/tapestry-trunk-freestyle/1263/changes
Changes:
[thiagohp] Implemented TAP55-2358 : OrderedConfiguration should have consistent
--
[...truncated 156 lines...]
warning:
