[
https://issues.apache.org/jira/browse/TAP5-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship updated TAP5-301:
--------------------------------------
Summary: When using the @Property annotation, Tapestry should throw an
exception rather than overwrite an existing method (was: When @Property
generated accessor methods will overwrite user generated accessors then either
warn the user or do not generate them.)
> When using the @Property annotation, Tapestry should throw an exception
> rather than overwrite an existing method
> ----------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-301
> URL: https://issues.apache.org/jira/browse/TAP5-301
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.15
> Reporter: Joel Halbert
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.16
>
>
> Occasionally I get stung when I declare an @Property on my page and then at
> some point later I create custom accessor methods for the property - which of
> course are never invoked since the @Property generated code wipes over them.
> I realise this is pretty minor, and all of my own doing, but I think a small
> amount of pain might be saved if T5 either:
> a) warns when @Property is declared at the same time as accessor methods for
> the property are defined.
> b) does not generate accessor methods when user defined methods are already
> present.
--
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]
