Date format error in LOV with dates. Jdeveloper 11.1.1.0.1

Question

We're facing a silly problem, which no one else seems to have... ?
When creating a LOV on a date column (eg hr.employees.hiredate) populated from another DataSource (eg. hr.job_history.startDate), the Application Module is working fine when tested.
Building a jspx on top of the Datacontrol picks up the LOV defined and creates a SelectOneChoice for hiredate. But for what ever value you select, it will complain about wrong date format "Error: The date is not in the correct format".
I can see, that the "real" value selected from the SelectOneChoice is an index-value, and the "format checking code" builtin to Jdeveloper can't figure out how to get the datevalue for the selected index.
Surely it must be me, who can't see the forest for the trees?
Thanks in advance :)

Answer 1

Its a bit tricky - but its doable... We have to abandon the "Oracle LOV model" to make it work.
Surely its must be some kind of bug in the Oracle LOV model? ?
The way to do it is like:
In Model project:
M1: Remove List Of Value binding from Model layer (Business components). Both entity and view if declared both.
M2: Create a view for the "date list" - ie the datasource for possible values in list.
M3: Secure that format mask (hint) for all dates involved are the same.
In View project:
V1: Drop datacontrol on jspx as normal input dates.
V2:Go to bindings for the page, and add (+) a new TABLE binding (And from here an iterator) to the view containing the list.
Modify the input dates you want to be list:
V3: Select the input date and rightclick and choose "convert"
V4: Select a SelectOneChoice component
V5: Pick the right column (tree) value to show in the SelectOneChoice componet.
Switch to source view:
V6: Drop a ForEach item from the component Palette (ADF Faces -> operations) on the SelectOneChoice (easiest to drop in structure windows)
V7: Drop a Select Item from the component Palette (ADF Faces -> common components) on the SelectOneChoice (easiest to drop in structure window).
Modify the source:
V8: Insert "items" and "var" attributes in ForEach like this: +"items="#{bindings.[[Here goes the name of the New TableBinding component you made in Step V2]].rangeSet}" var="li"+
V9: Insert "value" attribute and change "label" attribute to reference your new list variable "li" like this: +label="#{li.[[here goes the name of the new TableBinding Component attribute (columnname) you made in Step V2]]}" value="#{li.Firstofmonth}"+
V10: Insert/edit any converters/validators needed for input validation.
Done....
You should end up with a SelectOnChoice definition (in your jspx file) something like this one:
+<af:selectOneChoice value="#{row.bindings.ActiveFrom.inputValue}"+
+label="#{row.bindings.ActiveFrom.label}"+
+required="#{bindings.McAccountsView1.hints.ActiveFrom.mandatory}"+
+shortDesc="#{bindings.McAccountsView1.hints.ActiveFrom.tooltip}">+
+<af:forEach items="#{bindings.FirstOfMonth1.rangeSet}" var="li">+
+<af:selectItem label="#{li.Firstofmonth}" value="#{li.Firstofmonth}" />+
+</af:forEach>+
+<af:convertDateTime pattern="dd-MM-yyyy"+
+messageDetailConvertDate="Its not possible to convert the date in {0} since its value {1} dont conform to the pattern {2}"+
+secondaryPattern="yyyy-MM-dd"/>+
+</af:selectOneChoice>+
And a binding definition (in your pagedef file) something like this one:
+<?xml version="1.0" encoding="UTF-8" ?>+
+<pageDefinition xmlns="http://xmlns.oracle.com/adfm/uimodel"+
+version="11.1.1.52.5" id="McAccounts01PageDef"+
+Package="solution">+
+<parameters/>+
+<executables>+
+<iterator Binds="McAccountsView1" RangeSize="25"+
+DataControl="dateLovEmailDataControl"+
+id="McAccountsView1Iterator" ChangeEventPolicy="ppr"/>+
+<searchRegion Binds="McAccountsView1Iterator" Criteria=""+
+Customizer="oracle.jbo.uicli.binding.JUSearchBindingCustomizer"+
+id="McAccountsView1Query"/>+
+<iterator id="FirstOfMonth1Iterator" RangeSize="10" Binds="FirstOfMonth1"+
+DataControl="dateLovEmailDataControl"/>+
+</executables>+
+<bindings>+
+<tree IterBinding="McAccountsView1Iterator" id="McAccountsView1">+
+<nodeDefinition DefName="dk.hammerJakobsen.Jdev.sample.model.McAccountsView">+
+<AttrNames>+
+<Item Value="EmployeeName"/>+
+<Item Value="Id"/>+
+<Item Value="BankAccount"/>+
+<Item Value="StellarAccount"/>+
+<Item Value="ActiveFrom"/>+
+<Item Value="ActiveTo"/>+
+</AttrNames>+
+</nodeDefinition>+
+</tree>+
+<action IterBinding="McAccountsView1Iterator" id="CreateInsert"+
+RequiresUpdateModel="true" Action="createInsertRow"/>+
+<action IterBinding="McAccountsView1Iterator" id="Delete"+
+RequiresUpdateModel="false" Action="removeCurrentRow"/>+
+<action IterBinding="McAccountsView1Iterator" id="First"+
+RequiresUpdateModel="true" Action="first"/>+
+<action IterBinding="McAccountsView1Iterator" id="Last"+
+RequiresUpdateModel="true" Action="last"/>+
+<action IterBinding="McAccountsView1Iterator" id="Find"+
+RequiresUpdateModel="true" Action="iteratorFind"/>+
+<action IterBinding="McAccountsView1Iterator" id="Execute"+
+RequiresUpdateModel="true" Action="iteratorExecute"/>+
+<action id="Commit" RequiresUpdateModel="true" Action="commitTransaction"+
+DataControl="dateLovEmailDataControl"/>+
+<action id="Rollback" RequiresUpdateModel="false"+
+Action="rollbackTransaction" DataControl="dateLovEmailDataControl"/>+
+<table IterBinding="FirstOfMonth1Iterator" id="FirstOfMonth1">+
+<AttrNames>+
+<Item Value="Firstofmonth"/>+
+</AttrNames>+
+</table>+
+</bindings>+
+</pageDefinition>+
this approach works... But... Its important to remember that the "two" values are different now. The value in the row, and the possible value from the list. When you select a new value for the row from the list, you'll have to commit the value before its in the row - even seen from Faces. You can't reference the value in the base table in a validator before the row is committed.
For the same reason I'll advise, that you only use the model in Single row view, since its can behave a bit funny in table views, where there's a lot of PPR.