I'm not certain this change happened from 4.1 to 4.1.1 as I'm pretty sure I never made it. Maybe from 3 -> 4 ?
The list is stored in the form ~specifically~ so that it does match exactly on render/rewind as anything else would be un-predictable . You can set volatile=true on your list -> but if you are using hibernate you really want to make use of the converter parameter to encode the very minimum amount of data necessary to re-constitute your entity list. On 3/12/07, Robert J. Walker <[EMAIL PROTECTED]> wrote:
I just upgraded from Tapestry 4.1 to 4.1.1. Now I'm having some problems with the For component. It seems that it was changed so that it stores the source list in hidden fields in the page and uses the stored version on rewind. I can understand why this might be useful, since it could be problematic if the source list changed on you between render and rewind. That being said, it causes two really big problems for me: 1. The download size of the page just got enormous. 2. The source list contains Hibernate entities, which are now detached on the rewind, causing errors. What I really want is the old behavior, which is to reload the list every time. I'll deal with the consequences of the list changing. Is there some way to get that behavior back, short of making my own component that subclasses ForBean and overrides getData()? Robert J. Walker --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
