Thank you so much, Shing. The problem was indeed with object equality
in Java. I implemented the methods and now I'm able to retrieve the
values of the model objects on submit.
And thanks Nick, for pointing me to the correct implementation of
using the selection models with custom objects.
You might like to try to implemented your own equal
method in UserDepartment.java.
Shing
--- Waimun Yeow <[EMAIL PROTECTED]> wrote:
> Yes, indeed the two selection models are suspicious.
> I used
> PropertySelection to test DepartmentSelectionModel
> and the value
> displayed by @Inser
Yes, indeed the two selection models are suspicious. I used
PropertySelection to test DepartmentSelectionModel and the value
displayed by @Insert shows the correct value of the selected entry
but the list did not generate selected="selected" for the entry after
submit and hence fell back to
UsersByDepartmentSelectionModel.java (and
DepartmentSelectionModel.jav)
looks suspcious.
The UsersByDepartmentSelectionModel.getOption method
returns a value
from userLists, but
UsersByDepartmentSelectionModel.translateValue returns
a value using a dao.
You might like to test
UsersByDepa
The second version of the demo helped me to correct the way custom
objects are passed in the selection property model classes. I have
made the changes in my selection model classes and also the
pageBeginningRender() method. However, I am still having the same
problem. I have posted the .pa
Hi Waimin.
> The BikeMaker example above uses StringPropertySelectionModel and
> String[] objects for the drop-down selection lists. However, I modified
> my program to use custom PropertySelectionModel(s) and custom objects
> as value objects in the models.
There are two versions of the demo
