On Tue, 15 Jul 2014 06:28:46 -0300, Geoff Callender <geoff.callender.jumpst...@gmail.com> wrote:

If I read Bob right, I think Bob said his problem was not due to nulls, it was due to the selected value not being one of the values in the OptionModel.

This can be caused by the lack of a good implementation of equals() and hashCode(), which almost every non-service class should have anyway, specially the ones which can appear inside collections (and SelectModel is a sort of collection of OptionModels).

--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to