[ https://issues.apache.org/jira/browse/TAP5-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346912#comment-14346912 ]
Jochen Kemnade edited comment on TAP5-2459 at 3/4/15 2:16 PM: -------------------------------------------------------------- I just tested that with 5.4-beta-28 and could not reproduce the issue, the setter is called there. was (Author: jkemnade): I just tested that with 5.4 and could not reproduce the issue, the setter is called there. > Setter in subinterface of getter's interface not found by tapestry > ------------------------------------------------------------------ > > Key: TAP5-2459 > URL: https://issues.apache.org/jira/browse/TAP5-2459 > Project: Tapestry 5 > Issue Type: Bug > Components: tapestry-core > Affects Versions: 5.3.7 > Reporter: Vincent Dhellemmes > Priority: Minor > > When a setter is declared in a subinterface of the interface containing the > associated getter, tapestry can't access to the setter and see the property > in read-only. > By example, if I have the following objects : > public interface ReadableObject { > String getValue(); > } > public interface ReadableWritableObject extends ReadableObject { > void setValue(String v); > } > When I reference an object of type ReadableWritableObject in a form, I have > the following error at the form validation : > "Expression 'readableWritableObject.value' for class > myPackage.myComponentWithForm is read-only." > When I move the setter in the first Interface (ReadableObject), it works. > Is it a bug of tapestry 5.3.7 ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)