Issue With Changing VO File Binding Values Using JDeveloper's ADF VO Editor
Last updated on AUGUST 02, 2016
Applies to:Oracle JDeveloper - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Changing VO binding values using JDeveloper's ADF VO editor does NOT result in expected changes to the corresponding VO xml file.
Steps to reproduce:
This issue can be reproduced at will using Oracle JDeveloper 12c version 22.214.171.124.0 as follows:
1. Create a custom application and create an ADF Model Project in the application.
2. Create a new View Object in the project, and then in the "Initialize Business Components Project" dialog, select "Oracle" for the "Data Source" entry and then create a connection to Oracle HR schema.
3. In the first step of creating VO, select the "Custom SQL Query" value for "Data Source".
4. In the second step of creating VO, enter the sql string, "select * from jobs" in the sql text area and finish the other steps.
5. Double click the finished VO and edit it as follows:
Click the "Query" tab and change the "binding" value from "Oracle Named" to "JDBC Positional" in the "Overview" view of IDE.
6. Review the corresponding VO xml file.
Observe "BindingStyle" property value is still "OracleName", confirming the modification made using the VO editor did not apply to the corresponding xml file.
FYI: Changing the binding value using the "Properties" window of the VO will change the value in the VO xml file.
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