You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Scott Walter (JIRA)" <ta...@jakarta.apache.org> on 2005/07/25 00:58:52 UTC

[jira] Updated: (TAPESTRY-436) Form Table not being updated properly

     [ http://issues.apache.org/jira/browse/TAPESTRY-436?page=all ]

Scott Walter updated TAPESTRY-436:
----------------------------------

    Attachment: ttest.zip

Demonstrates with problems I discussed in the issue

> Form Table not being updated properly
> -------------------------------------
>
>          Key: TAPESTRY-436
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-436
>      Project: Tapestry
>         Type: Bug
>   Components: Framework
>     Versions: 4.0
>     Reporter: Scott Walter
>     Priority: Blocker
>  Attachments: ttest.zip
>
> I have created and attached an example where a page that has a Form Table gets updated properly in 3.x, but does not in 4.0.  I have basic table that has two editable columns (Checbox and TextField).  When I edit values and click a submit button, the origial values are displayed in 4.0, but returns the updated values in 3.x.  What seems to be happening is under 4.0, when calling the set methods (after entering new values into the columns in the table) in the bean for the rows in the table it is referencing the bean at a different memory location from when I initiially created the instances of the bean.   This behaivor does not exist in the 3.x version.
> I have checked, double checked, and triple checked my code.  I have made sure about the following:
> 1.  No instances of the bean class are being created by me other than the initial population.  I have logging statements in my construtor of my bean class to make sure of this.
> 2.  I have properly implemented the IPrimaryKeyConvertor interface.
> This issue is near and dear to my heart, I have spent alot of time and energy trying to isolate this problem.  If there is any information that you would need, please feel free to contact me.  Like I said above, I have attached the same code that I have run against 3.0 and 4.0.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org