RichInputText Added Progammatically Is Coercing Blank Value For Number Type To Zero (Doc ID 2123917.1)

Last updated on APRIL 06, 2016

Applies to:

Oracle JDeveloper - Version 12.1.3.0.0 to 12.1.3.0.0 [Release 12c]
Information in this document applies to any platform.

Symptoms

RichInputText field has a problem when programmatically added to a Composite Component. When displaying the form, and the user leaves the field blank and clicks a button, rendering the response via the Converter.getAsString() returns the value 0, and so 0 is displayed in the field. This is not the desired behaviour.

RichInputText field is added to a form programmatically like:

it works as desired, in that a blank field will remain displayed as blank when a button is clicked and the field is rerendered.
It appears that adding the markup causes ADF to do something special that it doesn't do when the RichInputText is added programmatically.

OBSERVATIONS
When adding programmatically, it can be seen that org.apache.myfaces.trinidad.bean.FacesBeanImpl._expressions field contains the corresponding ValueExpression with the value of "#{cc.attrs.bean.age}" whereas when adding via markup, the ValueExpression has a value of the form "//C:/system12.1.3.0.41.140521.1008/o.j2ee/drs/EarName/WebAppName.war/resources/ea/ea.xhtml @76,42 value="#{cc.attrs.bean.age}""

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