Hi Stephan, > Of course a user should not be assigned twice > to a job. This sounds like a valid use case for a Set rather than a List. To achieve this implement a reasonable equals-Method for User and rewrite your Job-class/your helper Bean DisplayJob to return a Set. As implementation of Set use a LinkedHashSet. This keeps the order of elements on each iteration. If you could even write a reasonable compareTo()-Method for User or alternatively a Comparator you would be able to use SortedSet and as implementation a TreeSet. ... > <td t:type="loop" t:source="job.assignments" t:value="user" > t:encoder="jobEncoder"> > > <select t:type="select" t:id="job" t:model="userModel" t:value="user" > t:encoder="userEncoder" blankLabel="Unassigned" /> > > </td> ... This looks to me as if you were displaying all users that are allready assigned to a Job in a select box. You´d need a select box with the UN-assigned users to make it possible to add new ones to the Job. This select box should be a multi select box. I have never done this myself so all I can do for you is point you to the wiki article: http://wiki.apache.org/tapestry/Tapestry5MultipleSelectOnObjects
Hope this helps, nillehammer == http://www.winfonet.eu --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
