[
https://issues.apache.org/jira/browse/TAPESTRY-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davor Hrg updated TAPESTRY-2116:
--------------------------------
Attachment: TAPESTRY-2116-V2.patch
I've looked again in the source and found that you manualy skip added methods
when doing transformation of field access.
this is patch is a version that doesn't mess with claimed fields, and is less
intrusive.
synopsis:
Ive added a method
void addTransformableMethod(TransformMethodSignature signature, String
methodBody);
InternalClassTransformationImpl
marks a method transformable by adding it into _transformableMethods
when skipping added methods, extra check is made to see if the method is
transformable
> @Retain and @Persist should generate a setter and/or getter for the decorated
> field
> -----------------------------------------------------------------------------------
>
> Key: TAPESTRY-2116
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2116
> Project: Tapestry
> Issue Type: New Feature
> Components: tapestry-core
> Reporter: Sven Homburg
> Fix For: 5.0.11
>
> Attachments: TAPESTRY-2116-V2.patch, TAPESTRY-2116.patch
>
>
> sometime code looks incredible unclear, because its peppered with getter and
> setter methods.
> i think it should be ease to extend the Persist- and RetainWorker for doing
> that job.
> @Retain(getter=true, setter=true)
> as an exmaple
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
