leaving aside how you created the web service, we can simplify the case to a method exposed on a SOAP service that returns a list in response. The multiple select option actually would not be quite helpful in this case as the list is not a collection you can update but just a set of values. The most common use case for select lists is to update an attribute of an updatable collection. Is this your use case as well? In this case you would drag the attribute you want to update as a select list and then use the dynamic list binding to associate it with the iterator providing the seletable values. In MAF there is an intermediate step required (here it differs from ADF) which is that you need to create the iterator before you can create the SOC. If you did not create the iterator, just create a new iterator in teh PageDef file (from the binding editor). If I recall correct then you need to create a new accessor iterator for the result (which then also explains why you cannot create a select component directly from it). When you created this drag and drop the attribute to update as a select choice and wire it to the iterator you built.
Hope this makes sense
Hi Frank, thanks for your reply.
I am trying to create a list (select one choice) containing all the weeks in a school year. When the user select a week, the time schedule for this week are displayed. If I try to create the list from a attribute instead of a collection, I get to choose between Dynamic List, Fixed List and Model Driven list. I don't think I can use any of those. At least I don't understand how.
As a temprary solution I am using a panel splitter with the result set populated as a MAF List View, this works, but it takes more space than a select one choice list. And the time schedule needs all the horizontal space.
Do you have an idea of how I can achieve this?