SOA Composite Editor 11g: Task Wizards do not Respect the Data Types Defined in the .xsd (Doc ID 1323136.1)

Last updated on OCTOBER 18, 2016

Applies to:

Oracle SOA Platform - Version: 11.1.1.1.0 and later   [Release: 11gR1 and later ]
Information in this document applies to any platform.

Symptoms

The forms generated by "Auto Generate Task Form" or "Task Form Wizard" do not respect the data types defined in the .xsd.
The element data types are not created correctly.

The generated UI (taskDetails.jspx)

<af:panelFormLayout id="pfl5">
   <af:inputText value="#{bindings.name.inputValue}"
     label="#{bindings.name.hints.label}"
     required="#{bindings.name.hints.mandatory}"
     columns="#{bindings.name.hints.displayWidth}"
     maximumLength="#{bindings.name.hints.precision}"
     shortDesc="#{bindings.name.hints.tooltip}"
     id="it1">
   <f:validator binding="#{bindings.name.validator}"/>
   </af:inputText>

   <af:inputText value="#{bindings.datum_von.inputValue}"
     label="#{bindings.datum_von.hints.label}"
     required="#{bindings.datum_von.hints.mandatory}"
     columns="#{bindings.datum_von.hints.displayWidth}"
     maximumLength="#{bindings.datum_von.hints.precision}"
     shortDesc="#{bindings.datum_von.hints.tooltip}"
     id="it2">
   <f:validator binding="#{bindings.datum_von.validator}"/>
   </af:inputText>
</af:panelFormLayout>


The field datum_von should be generate as: af:inputDate.

This incorrect definition would lead to the acceptance of non-date values when the task form is edited from the WorkList application.
Another side effect is that the "popup date picker" is not generated in WorkList application to input dates easily.

However, a simple workaround of editing the .jspx file from af:inputText to af:inputDate resolves the issue.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms