phillip rhodes wrote:
I have a lot of domain objects that I display using the select component. I
used to have a lot of implementations of IPropertySelectionModels floating
around in my app (one for each domain object type).
I created a simple interface that each of my domain objects implemented (getLabel) and created an implementation of IPropertySelectionModels that processed list items of this type.
Here are links to 2 files:
http://www.rhoderunner.com/viewcvs/viewcvs.cgi/jsso/src/java/org/jsso/tapestry/SelectionModel.java?rev=1.3&content-type=text/vnd.viewcvs-markup
http://www.rhoderunner.com/viewcvs/viewcvs.cgi/jsso-om/src/java/org/jsso/ISelectModelItem.java?rev=1.1&content-type=text/vnd.viewcvs-markup
Let me know your thoughts, and of course I volunteer to add it to the repo if I
get cvs access.
Phillip
Phillip Rhodeshttp://www.jsso.org Open source Java Identity and Authorization
Serviceshttp://www.rhoderunner.com Open Source Java Ecommerce Suite
I rather promote mine, using reflection (or code generation if anyone
steps up to it and think performance is an issue):
http://issues.apache.org/jira/browse/TAPESTRY-628
Check it out, it avoids you the need of making your domain objects
implement an interface.
--
Ing. Leonardo Quijano Vincenzi
Director Técnico
DTQ Software
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
