Thanks a lot. The volatile parameter did not help in my situation. I created a bug in the tapestry bug tracking DB: TAPESTRY-691<http://issues.apache.org/jira/browse/TAPESTRY-691> .
Thanks again for the help. Ji On 10/4/05, Mind Bridge <[EMAIL PROTECTED]> wrote: > > Hi, > > I am aware of this issue and was trying to find the > best way to resolve it. Since it is rather rare > (depends on the contents of the columns as well, not > only the dynamic nature of the columns string) it was > a bit on the back burner. > > Please add a bug report for this -- I am finishing the > documentation of the Table components this week and > will fix that problem as well. > > In the meantime, please try the following parameter to > your table: > > <binding name="volatile" value="false"/> > > This might help, even though it is not the ideal > solution. > > -mb > > --- Ji Wang < [EMAIL PROTECTED]> wrote: > > > I'm using Table component to create a table in my > > page. > > > > My component configuration is like this: > > <component id="dependentInformationTable" > > type="contrib:Table"> > > <binding name="source" value="dependents"/> > > <binding name="columns" value="columnsString"/> > > <binding name="row" value="dependentLineItem"/> > > <binding name="pageSize" value="10" /> > > <binding name="rowsClass" > > value="beans.evenOdd.next"/> > > </component> > > > > columnsString is passed in dynamically at runtime. > > Right now, if I resubmit > > the page, and return different column number for the > > table, tapestry gives > > me stale Link error. Any idea how to fix this? > > > > Thanks a lot. > > > > Ji > > > >
