[
https://issues.apache.org/jira/browse/TAPESTRY-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAPESTRY-2567.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.15
Assignee: Howard M. Lewis Ship
> Tapestry doesn't identify conflicting annotations on component fields
> ---------------------------------------------------------------------
>
> Key: TAPESTRY-2567
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2567
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.14
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.15
>
>
> Currently, as the worker for an annotation is activated for a particular
> field, the field is "claimed" by the annotation.
> When searching for fields with a given annotation, previously claimed fields
> are ignored.
> Thus if you use conflicting annotations, such as @Persist and @Parameter, you
> get no error and it's a guess as to which takes effect.
> Instead, we should see a failure when the second annotation work tries to
> re-claim the field. The exception should identify how the field was claimed,
> for example, by identifying the annotation (or at least, annotation type) for
> which the field was claimed.
--
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]
