Return-Path: 
 <commits-return-24090-apmail-tapestry-commits-archive=tapestry.apache.org@tapestry.apache.org>
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 3C03C17307
	for <apmail-tapestry-commits-archive@minotaur.apache.org>;
 Mon, 23 Mar 2015 15:44:18 +0000 (UTC)
Received: (qmail 66483 invoked by uid 500); 23 Mar 2015 15:44:11 -0000
Delivered-To: apmail-tapestry-commits-archive@tapestry.apache.org
Received: (qmail 66443 invoked by uid 500); 23 Mar 2015 15:44:11 -0000
Mailing-List: contact commits-help@tapestry.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@tapestry.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@tapestry.apache.org>
List-Post: <mailto:commits@tapestry.apache.org>
List-Id: <commits.tapestry.apache.org>
Reply-To: dev@tapestry.apache.org
Delivered-To: mailing list commits@tapestry.apache.org
Received: (qmail 66434 invoked by uid 99); 23 Mar 2015 15:44:11 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Mar 2015 15:44:11 +0000
Date: Mon, 23 Mar 2015 15:44:11 +0000 (UTC)
From: "Jochen Kemnade (JIRA)" <jira@apache.org>
To: commits@tapestry.apache.org
Message-ID: <JIRA.12686419.1388069315000.7053.1427125451639@Atlassian.JIRA>
In-Reply-To: <JIRA.12686419.1388069315000@Atlassian.JIRA>
References: <JIRA.12686419.1388069315000@Atlassian.JIRA>
 <JIRA.12686419.1388069315088@arcas>
Subject: [jira] [Closed] (TAP5-2268) @Property may generate a method that
 conflicts with an existing one, without error, and with unpredictable
 results
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/TAP5-2268?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jochen Kemnade closed TAP5-2268.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 5.4

Thanks!

> @Property may generate a method that conflicts with an existing one, with=
out error, and with unpredictable results
> -------------------------------------------------------------------------=
-----------------------------------------
>
>                 Key: TAP5-2268
>                 URL: https://issues.apache.org/jira/browse/TAP5-2268
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3.7, 5.4
>            Reporter: Alexey Chalov
>            Priority: Minor
>             Fix For: 5.4
>
>         Attachments: 0001-TAP5-2268-add-test-to-verify-that-this-issue-is=
-no-l.patch, 0005-TAP5-2268-Property-may-generate-a-method-that-confli.patc=
h
>
>
> Page class can contain 2 conflicting pieces for displaying html table lik=
e that:
> @Property(write=3Dfalse)
> private List<Item> items;
> or
> public GridDataSource getItems() {
>     ....
> }
> This causes no error then these 2 constructs present in page class, but b=
ehaviour is unpredictable: either accessor for GridDataSource or property g=
enerated accessor can be used when page is generated. Restarting/redeployin=
g application can change this behaviour to any of these 2 choices in unpred=
ictable manner. More oftenly (as I noticed 90% data source accessor is used=
 when table content is generated), but about ~10% is left on generated acce=
ssor. Tested under Tomcat 7.
> It would be nice if exception will rise in such situa=D0=B5ions to preven=
t accidental programming error.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)