Return-Path: Delivered-To: apmail-myfaces-users-archive@www.apache.org Received: (qmail 35276 invoked from network); 26 Jun 2007 00:12:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Jun 2007 00:12:39 -0000 Received: (qmail 30200 invoked by uid 500); 26 Jun 2007 00:12:41 -0000 Delivered-To: apmail-myfaces-users-archive@myfaces.apache.org Received: (qmail 29178 invoked by uid 500); 26 Jun 2007 00:12:39 -0000 Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Discussion" Delivered-To: mailing list users@myfaces.apache.org Received: (qmail 29167 invoked by uid 99); 26 Jun 2007 00:12:39 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jun 2007 17:12:39 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of awiner@gmail.com designates 64.233.162.236 as permitted sender) Received: from [64.233.162.236] (HELO nz-out-0506.google.com) (64.233.162.236) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jun 2007 17:12:34 -0700 Received: by nz-out-0506.google.com with SMTP id i28so1351397nzi for ; Mon, 25 Jun 2007 17:12:14 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=qxTuCiF/RfIKZPudcVJtlt64XXo8D0B5CtAlRtxQR8C+1+TcM/JkbGK3qxR+VpRNXKjr7xBGxO1HtnshrJZnRO1abZYQfXOrJKGg865vODAyjWkCqY3RZ/9MmYWjuMG18JJYjbyJYmC/ihxfzWDe5C4MR9NbMHPPrzC2OGxhkKY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=R9CbgGoHm76HGceotdtbAMcRGYW2KxfAXWGmZqJ/ca/1gagCF5/UP/ci4RJi2lqOFK49LXskW/gtrrHdz8tWWG9GGL48JyU+nzV38WYjCGT3IaTo44obqF371JkGhkqXIbKqjqnY76HwHU8cUwn+RJr5F0jPJRJBdB6xGdjUBX4= Received: by 10.115.78.1 with SMTP id f1mr5909008wal.1182816733787; Mon, 25 Jun 2007 17:12:13 -0700 (PDT) Received: by 10.115.18.12 with HTTP; Mon, 25 Jun 2007 17:12:13 -0700 (PDT) Message-ID: <6dac79b90706251712k5999e879kdf05ee9900524234@mail.gmail.com> Date: Mon, 25 Jun 2007 17:12:13 -0700 From: "Adam Winer" To: "MyFaces Discussion" Subject: Re: [Trinidad] Detailstamp facet problem In-Reply-To: <6dac79b90706251029l2d944439w47a9678d169105bc@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_13872_33338276.1182816733753" References: <464DB92F.3050806@kava.be> <4655339D.7050308@kava.be> <467B9BFE.8090401@kava.be> <6dac79b90706251011p5bddbcbdie32df205ed6119b1@mail.gmail.com> <6dac79b90706251029l2d944439w47a9678d169105bc@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_13872_33338276.1182816733753 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline OK, the detailStamp bug is fixed. -- Adam On 6/25/07, Adam Winer wrote: > > I've filed the detailStamp bug as: > > http://issues.apache.org/jira/browse/TRINIDAD-75 > > It repros in the Trinidad demo bundle too. > > -- Adam > > > On 6/25/07, Adam Winer wrote: > > On 6/22/07, Henk Vanhoe wrote: > > > Finally, I have found some time to make a testproject where this > problem > > > (bug?) can be duplicated... > > > > > > There is a jsp in this project > > > (/detailstamptest/faces/table/changeTable.jspx) which consists of a > > > table with one element. Next to this element there is a 'Show detail' > > > link. When you click on this link you see a new table with two > > > addresses. When you close the detail and reopen it, the detail-table > is > > > empty and there are some error-messages in the logs ("Exception while > > > determining read-only state of value-binding"). > > > > > > This problem can be solved by changing the > > > org.apache.myfaces.trinidad.CLIENT_STATE_METHOD param in web.xml from > > > "all" to "token". > > > > I can reproduce this. It's strange - I assume it's a serialization > > issue somewhere in the table state saving code, but just a guess. > > > > > However, now there is a new problem... When you open > > > the detail, change one of the street-names, close the detail again and > > > then hit the save-button you can see in the log-messages that the > > > changes are not submitted to the server! When you leave the detail > open > > > and hit the save-button, the changes are submitted... > > > > The tables have immediate="true" on them, which means that the > > values aren't pushed to the model when you toggle the table. > > Remove immediate="true". > > > > -- Adam > > > ------=_Part_13872_33338276.1182816733753 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline OK, the detailStamp bug is fixed.

-- Adam


On 6/25/07, Adam Winer <awiner@gmail.com> wrote:
I've filed the detailStamp bug as:

http://issues.apache.org/jira/browse/TRINIDAD-75

It repros in the Trinidad demo bundle too.

-- Adam


On 6/25/07, Adam Winer <awiner@gmail.com> wrote:
> On 6/22/07, Henk Vanhoe <Henk.Vanhoe@kava.be> wrote:
> > Finally, I have found some time to make a testproject where this problem
> > (bug?) can be duplicated...
> >
> > There is a jsp in this project
> > (/detailstamptest/faces/table/changeTable.jspx) which consists of a
> > table with one element. Next to this element there is a 'Show detail'
> > link. When you click on this link you see a new table with two
> > addresses. When you close the detail and reopen it, the detail-table is
> > empty and there are some error-messages in the logs ("Exception while
> > determining read-only state of value-binding").
> >
> > This problem can be solved by changing the
> > org.apache.myfaces.trinidad.CLIENT_STATE_METHOD param in web.xml from
> > "all" to "token".
>
> I can reproduce this.  It's strange - I assume it's a serialization
> issue somewhere in the table state saving code, but just a guess.
>
> > However, now there is a new problem... When you open
> > the detail, change one of the street-names, close the detail again and
> > then hit the save-button you can see in the log-messages that the
> > changes are not submitted to the server! When you leave the detail open
> > and hit the save-button, the changes are submitted...
>
> The tables have immediate="true" on them, which means that the
> values aren't pushed to the model when you toggle the table.
> Remove immediate="true".
>
> -- Adam
>

------=_Part_13872_33338276.1182816733753--