Actually, you should use persistent properties for these. That way when someone adds form #3 to the page no special work is needed.
jeff -----Original Message----- From: Rob Dennett [mailto:[EMAIL PROTECTED] Sent: Thursday, January 05, 2006 3:12 PM To: Tapestry users Subject: RE: Weirdness NEVERMIND I realize that the answer is that the only when a form is submitted, the only parameters passed to the server are the ones in that form. I guess the other way to deal with the problem is to use a Hidden component to store another form's property in that form. Thanks for your help, Rob -----Original Message----- From: Rob Dennett Sent: Thursday, January 05, 2006 5:02 PM To: Tapestry users Subject: Weirdness I was getting a weird error and when I discovered the cause, I wanted to know why things are handled this way. I had a page with two forms on it, the first being a simple search form and the second containing a list of search results and a button next to each which performs an action on that item. When the action button is clicked, I wanted the app to return the same search results and have the same value in the search field. There is a set of accessor methods for the search string. Calling the getter from within the listener for the action button returned null even though there was text in the search field. I found out that I had to put everything in one big form in order to access the text in the text field. I guess I also could have accessed the component and gotten the value that way, or made the search string property persistent. What I don't understand is why when the first form is being rewound, it doesn't set the search string property with the value of the text field. It's like it doesn't get rewound at all. Is this what is happening? Why? Thanks, Rob Dennett -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.14.12/220 - Release Date: 1/3/2006 -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.14.12/220 - Release Date: 1/3/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.14.12/220 - Release Date: 1/3/2006 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
