[
https://issues.apache.org/jira/browse/TAP5-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14349525#comment-14349525
]
Thiago H. de Paula Figueiredo commented on TAP5-2459:
-----------------------------------------------------
Hello, guys!
[~chrispoulsen] and [~jkemnade] are correct: Java's Introspector doesn't find
some getters and setters and Tapestry does catch some cases Introspector
doesn't. I've discussed this in the Tapestry dev mailing list:
http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/Abandon-java-beans-Introspector-or-keep-working-around-it-td5727399.html.
It's very probable I've already fixed this issue, as this looks like a
duplicate of TAP5-1548 (which is about a getter) and similar to TAP5-1885
(which is about a setter).
[~Vincent D.], please check with a Tapestry 5.4 beta.
Cheers!
> 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)
