SelectOneChoice and selectItem foreach row - Not selecting current value

Question

Hi -
I am having a problem whereby the list that is rendered in the UI is not selecting my current ID...It is just showing the "blank" selection, which is another problem - it must be mandatory.
The UI shows the list (from my iterator) but nothing is selected on the list, even thow the ROWs do have a ClasscategorytypeId assigned to them.
My Iterator that feeds the list is defined in the PageDef as follows:
<iterator id="ClasscategorytypeView1Iterator" Binds="ClasscategorytypeView1"
RangeSize="-1" DataControl="AppModuleDataControl"/>
</executables>
Here is the column definition.
<af:column sortable="false" headerText="ClassCategory"
binding="#{backing_svrclass_edit_list.column3}"
id="column3">
<af:selectOneChoice value="#{row.ClasscategorytypeId}"
required="true">
<af:forEach var="item" items="#{bindings.ClasscategorytypeView1.rangeSet}">
<af:selectItem
value="#{item.ClasscategorytypeId}"
label="#{item.Name}"/>
</af:forEach>
</af:selectOneChoice>
</af:column>

Answer 1

Hi Frank - thanks for the feedback.
for #1 - setting the defaults on the entity and view object didn't help. It still shows up with a "BLANK" field (don't want the blank field, since "required"), and it is not selecting the correct option that cooresponds to the ID from the ROW.
re #2 - I don't understand solution #1 that he mentions? Here is the quote:
"Create a second binding to the same attribute that the list binding is for. But make this a plain attribute binding. This binding will map direct to the real value of the column so you can use this second binding as a proxy to the list in your expressions. Note the binding just has to be created in the PageDef file, it does not need to be displayed on the page itself." These parts are confusing to me:
"Create a second binding...", "use this second binding as a proxy"...I thought that you can have only one binding per control, and second, re: the proxy item - is this implying that I have to setup an onload and onclick event, and somehow map the option items (zero based index) to the real value both when showing the list (and selecting the right one) and processing the currently "selected" item? This sounds like a very combursome thing to do...? Can you clarify that for me?
(if you had a simple example that would be great!)
Thanks again!
I really appreciate it.
ps. I found the #1 scenario (foreach solution) from the Steve Muench blog here, and if I am to understand this correctly - even his sample is misleading, since the list values returned from the query are zero based, and NOT value based.. so he must have aligned these values in the database to be ZERO based and coorespond to the behaviour of rendering the list... This is very misleading.
Here's the URL:
http://www.oracle.com/technology/products/jdev/tips/muench/screencasts/editabletabledropdown/dropdownlistineditabletable.html?_template=/ocom/technology/content/print