You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Josh Canfield (JIRA)" <ji...@apache.org> on 2011/08/29 22:39:38 UTC

[jira] [Commented] (TAP5-1623) @Parameter and @Property mutually exclusiv?

    [ https://issues.apache.org/jira/browse/TAP5-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093181#comment-13093181 ] 

Josh Canfield commented on TAP5-1623:
-------------------------------------

is the problem that adding @Property causes the setter to not get called, or that @Parameter doesn't call the setter either way?

> @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