[
https://issues.apache.org/jira/browse/TAP5-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348364#comment-14348364
]
Chris Poulsen commented on TAP5-2459:
-------------------------------------
I've had trouble with getter/setter detection some times. When I finally dug
into it, it turned out to be the Introspector class from java that was the
culprit (in my case (java6) it was unable to detect a valid setter if another
setter method with 2 parameters was present. The issue was not present in java7
iirc.
This sounds a bit like it could be related.
> 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)
