Often the introduced methods have privileged access to fields,
bypassing things like FieldConduits often, the introduced methods
are how the FieldConduits are themselves implemented. Not excluding
them from the field transformation step (where reads and writes of
fields are converted into
On 23 Apr 2012, at 16:50, Howard Lewis Ship wrote:
Often the introduced methods have privileged access to fields,
bypassing things like FieldConduits often, the introduced methods
are how the FieldConduits are themselves implemented. Not excluding
them from the field transformation
On 20 Apr 2012, at 19:00, Howard Lewis Ship wrote:
On Fri, Apr 20, 2012 at 9:39 AM, Luke Wilson l...@viscri.co.uk wrote:
More is described here:
http://stackoverflow.com/questions/10249254/tapestry-5-3-plasticclass-getmethods-doesnt-include-introduced-methods.
Ah, yes, I can see what
Hi,
The behaviour of the now deprecated ClassTransformation.matchMethods() and
related methods has changed to not include introduced Methods. I believe this
problem also applies to fields.
On top of this, the built in ClassTransformationWorker2s use
PlasticClass.getMethods() directly to find
On Fri, Apr 20, 2012 at 9:39 AM, Luke Wilson l...@viscri.co.uk wrote:
Hi,
The behaviour of the now deprecated ClassTransformation.matchMethods() and
related methods has changed to not include introduced Methods. I believe
this problem also applies to fields.
On top of this, the built in
