Me:
I suppose the usual approach is to trigger the download of
IDataProvider's data via the event handler of the submit button.
That way, the data would be available for both Iterator
IDataProvider.iterate(first, count) and int IDataProvider.size().
Eelco Hillenius Sent: Tuesday, April 04,
no, the model() is there to wrap every object returned from the iterator() call in its own (detachable) model. this model is used in Item components which represent a rows inside a dataview.-Igor
On 4/5/06, Frank Silbermann [EMAIL PROTECTED] wrote:
Me: I suppose the usual approach is to trigger
I suppose the usual approach is to trigger the download of IDataProvider's
data via the event handler of the submit button. That way, the data would
be available for both Iterator IDataProvider.iterate(first, count) and
int IDataProvider.size().
It's the responsibility of the model(s).
I suppose the usual approach is to trigger
the download of IDataProviders data via the event handler of the submit
button. That way, the data would be
available for both Iterator IDataProvider.iterate(first,
count) and int IDataProvider.size().
However, I do not have a single submit
there is nothing to trigger for idataprovider. whenever the datatable renders it will call the appropriate methods. simply make your dataprovide have a reference to your form model and then use that as the criteria for quieries in both size and iterator.
-IgorOn 4/4/06, Frank Silbermann [EMAIL
