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
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
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
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 @Insert
I am using the DynamicSelectionList (Tap 3) component managed at the
Tassel site http://equalitylearning.org/Tassel/app?service=direct/1/
Search/viewComponentsp=SmatmshDynamicSelectionList
I followed the BikeMaker demo with source code at http://
lombok.demon.co.uk/tapestryDemo/welcome
The
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 and
