Because individual options can be disabled.
Also, you shouldn't really use OptionModelImpl because it is
an internal class and may change in the future.
(1) You can pass a map (names to codes) and Tapestry will create
the model for you.
(2) More work, implement the SelectModel interface. Daniel Jue
posted an interesting generic solution here:
http://www.phy6.net/wiki/tiki-index.php?page=Tapestry+5+GenericSelectionModel
Cheers,
Nick.
Allen Guo wrote:
I changed
OptionModel option = new OptionModelImpl(obj.getName(), true,
obj.getCode());
to
OptionModel option = new OptionModelImpl(obj.getName(), false,
obj.getCode());
It works fine. But I don't know why OptionModelImpl construction need
the second parameter.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
