Yes (assuming that they contain different data), but your
IPropertySelectionModel should ideally present a "view" of your
collection - so you should easily be able to create a implementation
class to handle each type of collection.
Paul
Vinicius Carvalho wrote:
Well, once again I'm confused. Must I have one model for each
collection? What happens if I have dozens of collections that comes
from the Database?
Thanks
---------------------------------------------------------------------
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]
