Yes, I've seen that. I actually saw it before I implemented my
Enumerations package, but I specifically didn't adopt the
IPropertySelectionModel interface (although I made sure I provided
enough functionality to provide the data) because I wanted to provide
something more generic that could then be molded to your purposes
(Tapestry, Struts, Cayenne-based batch job, etc).
I'll definitely look at the Tapestry model when I get around to making
mine, though. Maybe I should've used the commons? :-)
From: Erik Hatcher [mailto:eri..hatchersolutions.com]
Sent: Monday, May 02, 2005 11:31 AM
Subject: Re: How to use Enums
On May 2, 2005, at 11:25 AM, Gentry, Michael (Contractor) wrote:
> Parts of it may seem a bit cumbersome, but I wanted something that
> log values nicely (hence part of the redundancy). When I have time, I
> also plan on putting together a Tapestry class that implements the
> IPropertySelectionModel interface, so that you can put the
> in a pulldown easily (with localization if I get ambitious).
There is already an EnumPropertySelectionModel in Tapestry. I don't
know if that suits your needs or not. I generally end up creating
custom IPropertySelectionModel's myself.
This archive was generated by hypermail 2.0.0 : Mon May 02 2005 - 11:49:33 EDT