[
https://issues.apache.org/jira/browse/TAP5-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093271#comment-13093271
]
Jens Breitenstein commented on TAP5-1623:
-----------------------------------------
It looks like the parameter write operation solely affects the class member but
ignores the property annotation. Accessing the getter from the page works as
usual (using getter when available). Thus I believe the @Property is not broken
in general when used with @Parameter, but a parameter silently ignores a
property annotation. From the debugger I guess T5 creates wrapper around
parameters and defers any activity until the parameter is first used and maybe
this wrapper code is not aware of a potential page @property?
> @Parameter and @Property mutually exclusiv?
> -------------------------------------------
>
> Key: TAP5-1623
> URL: https://issues.apache.org/jira/browse/TAP5-1623
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.6
> Reporter: Jens Breitenstein
> Priority: Minor
>
> in case a @parameter annotation is used in conjunction with @property the
> property setter is never called.
> the framework should either support it or reject such a combination of
> annotations.
> sample:
> @Property(read = true, write = false)
> @Parameter(required = true)
> private String _myParam;
> // ---->> NEVER CALLED
> public void String setMyParam(final String param)
> {
> _myParam = param;
> // do more...
> }
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
