OK, the detailStamp bug is fixed. -- Adam
On 6/25/07, Adam Winer <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> wrote: > On 6/22/07, Henk Vanhoe <[EMAIL PROTECTED]> 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 >
