[ https://issues.apache.org/jira/browse/TAP5-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901532#comment-14901532 ]
Thiago H. de Paula Figueiredo commented on TAP5-2489: ----------------------------------------------------- Hello, [~svein]! I'm sorry, but your interpretation of @Parameter.required is wrong. So is IntelliJ's. It means it should be bound, not that it should explicitly be defined in the template or @Component annotation. Here's the @Parameter.required JavaDoc[1]: "If true, the parameter is required and and must be bound. If false (the default), then the parameter is optional.". The default value for a parameter may be provided by the @Property.value or the return value of a method named "default[parameter name]". If a parameter has a default value, it's bound implicitly, but still bound. My only disagreement with [~jkemnade] is that this ticket should have been closed as Invalid, not Incomplete. :) [1] http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/annotations/Parameter.html#required() > Palette component parameter availableLabel and selectedLabel should have > required = false > ------------------------------------------------------------------------------------------ > > Key: TAP5-2489 > URL: https://issues.apache.org/jira/browse/TAP5-2489 > Project: Tapestry 5 > Issue Type: Wish > Components: tapestry-core > Affects Versions: 5.4 > Reporter: Svein > Priority: Minor > Labels: component > > Having value = "message:core-palette-available-label" and value = > "message:core-palette-selected-label" then @Parameter(required = false) is > better! My IDE gives me error when selectedLabel or availableLabel is skipped. -- This message was sent by Atlassian JIRA (v6.3.4#6332)