My memory isn't able to retain state knowledge of 4.1.1 reliably enough to have a clue on this, but if you try it on 4.1.2-SNAPSHOT and run into the same problem + file a jira issue I can probably fix whatever it is.
On 3/5/07, Andrea Chiumenti <[EMAIL PROTECTED]> wrote:
Hello, I've the following problem in Tapestry 4.1.1: I've a component that conditionally renders other components. With default components like TextField I've no problems, while if I try to ad an Autocompleter it seems that when the component is rendered no tapestry.widget.synchronizeWidgetState is called for it and, even if I can see the component when I click on the dropdown button an exception is thrown. How could I solve it ? Thanks, kiuma
-- 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]
