Just to clarify Paul's response a bit as it did not seem clear on
this... you can create a single custom IPropertySelectionModel class
to handle a wide range of data. In the past, I've created a general
purpose (within the scope of a particular project) JavaBean model
that allowed specification of the name path expression and value path
expression.
I'm pretty sure if you check the list archives for
IPropertySelectionModel you'll find several examples of this sort of
thing.
Erik
On Jun 4, 2005, at 12:43 AM, Paul Ferraro wrote:
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: tapestry-user-
[EMAIL PROTECTED]
---------------------------------------------------------------------
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]
