Return-Path: X-Original-To: apmail-tapestry-commits-archive@minotaur.apache.org Delivered-To: apmail-tapestry-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CF5291737F for ; Wed, 4 Mar 2015 14:17:12 +0000 (UTC) Received: (qmail 35114 invoked by uid 500); 4 Mar 2015 14:17:06 -0000 Delivered-To: apmail-tapestry-commits-archive@tapestry.apache.org Received: (qmail 35074 invoked by uid 500); 4 Mar 2015 14:17:06 -0000 Mailing-List: contact commits-help@tapestry.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tapestry.apache.org Delivered-To: mailing list commits@tapestry.apache.org Received: (qmail 35064 invoked by uid 99); 4 Mar 2015 14:17:06 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Mar 2015 14:17:06 +0000 Date: Wed, 4 Mar 2015 14:17:06 +0000 (UTC) From: "Jochen Kemnade (JIRA)" To: commits@tapestry.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (TAP5-2459) Setter in subinterface of getter's interface not found by tapestry MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/TAP5-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346912#comment-14346912 ] Jochen Kemnade commented on TAP5-2459: -------------------------------------- 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)