My Oracle Support Banner

After Upgrading to JDeveloper 11.1.1.3.0 Textitem Declarative Component Binding Stopped Working (Doc ID 1265240.1)

Last updated on DECEMBER 10, 2019

Applies to:

Oracle JDeveloper - Version 11.1.1.3.0 to 11.1.1.3.0 [Release Oracle11g]
Information in this document applies to any platform.

Symptoms

When trying to update a record using ADF custom declarative components in JDeveloper 11.1.1.3, it will not display new updated value from ViewObjet. In fact it prints out the record prior to the update.
In previous releases (i.e. JDeveloper 11.1.1.2) this functionality works where it always displays the record that was successfully submitted.

Example. If we have an application that contains a few updateable fields and if we were to update one of the fields and then press the [Submit] button it will the display record prior to submission instead of the new record just entered.

Value Return from component is::<Old Value>



The backing bean can contain an action to fetch the new value.

    public String cb1_action() {
        // Add event code here...
        FacesContext fc = FacesContext.getCurrentInstance();
        ELContext elc = fc.getELContext();
        ExpressionFactory ef = fc.getApplication().getExpressionFactory();
        ValueExpression ve =
            ef.createValueExpression(elc, "#{bindings.<ATTRIBUTE>.inputValue}",
                                     Object.class);
        System.out.println("Value Return from component is::" +
                           ve.getValue(elc));
        return null;
    }

Changes

Upgrade to JDeveloper 11.1.1.3.0.

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
 STEPS
 1. OPATCH instructions
 2. PATCH 9526007
 3. TEST FIX


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.