Oracle JDeveloper 12.1.2 Known Issues


This document contains a list of known issues (and, where applicable workarounds for those issues) for the following products:

  • Oracle JDeveloper 12c (
  • Oracle Application Development Framework (ADF) 12c (
  • Oracle Team Productivity Center (TPC) 12c (
  • Oracle ADF Essentials 12c (

For a list of new features in this release, see the What's New document on OTN.

This document describes known issues with the release. If and when new issues are discovered they will be added to this document. Please also use the JDeveloper community discussion forum and other community resources for questions and answers and to let us know what you think!


Please read the installation guide for details on system requirements and specific installation instructions for various platforms.

Installer Performance

There is a known issue in this release with the performance of the installer. The following occurs with the generic installer as well as the platform-specific installers. After the "Copy Files" phase, the installer generates client libraries for WLS. The generation of these libraries at install time improve the ability for Oracle to patch those libraries if needed. However, the trade-off is that more time is added to the overall installation process. The duration of this depends on the system being installed onto. Generally, more powerful systems will be able to complete this step more quickly. We've noticed that on some under-powered or otherwise over-taxed machines (for example Windows machines with 2GB RAM on Pentium4 processor), this part of the installation phase can take as long as 20 minutes. We recommend at least 4 GB RAM and a fast processor (for example Intel Core 2 i5 or equivalent).

Installer fails to start on Windows (17154525)

The JDeveloper 12c installer must be run as Administrator on Windows platforms. In some cases, not running as administrator can result in the installer failing to launch and you may see a message similar to "Error Launch: No such file or directory". As a work-around, right-click on the jdev_suite_121200_winXX.exe file and choose "Run as Administrator", or launch the exe from the command line of an elevated command window. error message

If you ran the script in Unix/Linux and received "syntax error" and/or "command not found" errors, you need to run the dos2unix command on After you have done this, should run without those errors.

Integrated WLS DefaultDomain not created on Windows Server 2012 (16844206)

The creation of DefaultDomain for Integrated WLS fails under Windows Server 2012. The workaround is to install WLS separately, and deploy to it from JDeveloper. 

EJB and JPA Components

The EJB wizard, Create Entities from Tables, does not execute the DDL and DML (14679071)

When running the "Entity Beans from Tables" wizard, if you configure the field, Attach an ID generator to each generated entity..., on the "General Options" page, you will need to manually configure the ID generator for the @SequenceGenerator or @SequenceGenerator options, depending on which one you select. For additional instructions, refer to the Javadoc generated into each entity class.

CDI does not work with JSF provided with ADF (16934790)

Contexts and Dependency Injection in Java EE 6 does not work in cases where JSF-based applications provide their own copy of the JSF libraries. This is the case with ADF in this release, and hence ADF Faces applications cannot use CDI in this release.

The getInitialContext() method is not generated when creating a Sample Java Client for a Session Facade that has business methods with parameters (16978775)

When you try to create a "Sample Java Client" for a Session Facade that has a business method(s) using any parameters, then the Java Client's getInitialContext() method will not be generated and an NPE will be thrown.

Here is the signature of the sample business method that will cause the issue:

List<Employees> getEmployeesFindBySal(Integer p_sal){

To work around this issue:

  1. Create a temporary "dummy" Session Facade that does not have business methods with parameters.
  2. Generate a Sample Java Client from dummy Session Facade.
  3. Copy the getInitialContext() method from that Java Client.

Database Development

JDBC-ODBC Bridge Database Connections (16800853)

The JDBC-ODBC Bridge connection type is not recommended for making database connections, and Oracle does not support use of the JDBC-ODBC Bridge driver. For more information, see

Text strings containing surrogate characters truncated when saving into a varchar field (16631663)

If you are using DB2 with the Oracle Datadirect JDBC driver you may find that the text field contents stored in DB2 database which contain supplementary characters are truncated.

This occurs because the version of Oracle Datadirect JDBC driver for DB2 ( (F000025.U000002)) included in 12.1.2 installation has a bug.  This issue has been fixed in the latest Oracle Datadirect JDBC driver for DB2.  Contact support to get an upgrade for the DB2 JDBC driver in your 12.1.2 application environment.


Using Forced Shutdown to Shut Down IntegratedWebLogicServer (16355918)

Shutting down IntegratedWebLogicServer may take more than 1 minute to ensure datasources have been written out. If you need to shut down the server fast you can use forced shutdown, but be aware that it kills the WebLogic domain process, running the risk of interrupting an active datasource and corrupting the data.

To use forced shutdown, go to Window > Application Servers > IntegratedWebLogicServer > Properties > Shutdown and choose "Shut Down Forcefully Always."

Custom ADF application Deployment requirements

If you have created a custom ADF application using JDeveloper, (not an Fusing Web Application, which has a predefined template), check to see if you have the following properties and files in your application:

  • A weblogic-application.xml file that includes an entry for ADFApplicationStateListener
  • A web.xml file that includes an ADFbindingFilter

    • Note that JDeveloper will automatically add the ADFBindingFilter only if a page definition file has been created during design time. If you do not see the ADFBindingFilter, you can add it manually.
  • An adf-config.xml file
    • Note that adf-config.xml is only created when ADF Page Flow features are added to the project in JDeveloper during design time. For instance, when you add a task flow or connection to the application, JDeveloper will create an adf-config.xml file. Adding ADF Business Components, ADF Model, or ADF Faces features do not generate an adf-config.xml file.

If any of these items are missing, you may receive an "Error 500: Internal Server Error" when you run the application. The first time you run this application, it may run correctly. But if you re-deploy and run this application again, you may get the error.

Web Services Development

Incorrect Sample Code in Documentation

The sample code illustrated in Example 23-7, "Attaching Policies to RESTful Web Service Clients Using Feature Classes," in "Developing and Securing Web Services," incorrectly uses the
com.sun.jersey.api.client.Client class. Instead, it must use the weblogic.jaxrs.api.client.Client class in order to support OWSM client policy attachment.

Error When Generating RESTful Client from a Remote WADL That References a JSON Schema (16715951)

You cannot generate a RESTful client from a remote WADL that references a JSON schema due to the version of library that is distributed with this JDeveloper release. The jsonschema2pojo library, on which it has a dependency, contains a bug that will cause a failure when attempting to generate a RESTful client if the WADL is not available on the local file system. The workaround is to copy the WADL and its resources locally and then generate the RESTful client from the local WADL.

Policy Not Enforced on a Provider Service Without a WSDL

For a web service provider with no WSDL associated with it, any policy attachments on it are not enforced by the server. To prevent users from deploying a Provider service without a WSDL, JDeveloper displays a warning in the code editor when this scenario is detected. The workaround for this problem is to maintain a WSDL for the Provider service and attach it to the service using the wsdlLocation annotation parameter.

Avoid Creating Multiple Top-down Web Services in the Same Project/Package (7165531)

Unless operating on the same schema, avoid creating multiple top-down web services in the same project as each successive top-down service may overwrite the ObjectFactory class created by the previous one if generated into the same package.

Deployment Fails When Deploying a JAX-WS RI Web Service to a Glassfish Server (14629256)

If you attempt to deploy a JAX-WS RI web service EAR or WAR file created using JDeveloper to Glassfish server, the deployment will fail.

To work around this issue, perform one of the following steps:

  • If your web service requires the web.xml file to support advanced capabilities, such as securing with basic authentication, then:
    • Edit the web.xml file to delete the oracle.adf.share.glassfish.listener.ADFGlassFishAppLifeCycleListener lifecycle listener entry, which is not required.
    • Delete the sun-jaxws.xml file.
  • Delete the web.xml file (if it is not required to support advanced capabilities).

Web Development

Deadlock (hang) in JSF Visual Editor on Mac OS (16734064)

Some users are reporting recurring deadlocks (hang) when using the JSF Visual editor on Mac OS. Oracle has investigated and found that most (if not all) these deadlocks occur due to interaction with 3rd party Mac OSX applications that install themselves through the OSX accessibility extensions, typically those that provide windows management features. The workaround for this release is to disable these 3rd party Mac OSX extensions through the System Preferences -> Security & Privacy -> Privacy tab - > Accessibility options. This should not effect screen readers and other real accessibility extensions.


ADF Business Components

ADF Business Components Runtime Parameter jbo.ampool.writecookietoclient Must Not be Modified (16846118)

The runtime ADF Business Components application module pooling parameter jbo.ampool.writecookietoclient is no longer required by ADF Business Components. Do not change the default value (false). The default is not to create a browser cookie. This parameter was formerly used to write the SessionCookie value to the client browser. This parameter also appears in the Enterprise Manager Fusion Middleware Control as AmpoolWritecookietoclient where its default value must not be changed.

Deprecated Usage of Method notifyUpdatedRow(ViewRowSetImpl, Row[], int[]) (15955245)

When overriding methods in the ViewImpl class of an ADF Business Components project, you must not override the "notify row updated" method with this signature:

(deprecated) protected void notifyRowUpdated(ViewRowSetImpl vrs, Row[]  viewRows, int[] attrIndices)

In JDeveloper the audit rule "notifyRowUpdated Method Parameters" will update all occurrences of this deprecated method to use the method with this signature instead:

(valid) protected void notifyRowUpdated(ViewRowSetImpl vrs, Row[]viewRows, int[] attrIndices, UpdateEvent updateEvent)

Note that it is important to check for code that calls the deprecated method and to change to the valid method (shown above). Specifically, make sure that the updateEvent parameter is added to the calling method.

Using the method with the updateEvent parameter ensures that the RowInconsistentException is thrown when two users attempt to change a row referenced by the same primary key from independent application module sessions.

ADF Security

ADF Security feature "Enable Identity Governance Framework" (IGF) is Currently Disabled (16852797)

The Configure ADF Security wizard displays a checkbox to enable Identity Governance Framework (IGF). The wizard displays this feature as unselected by default. However, when you select the checkbox no additional functionality is currently provided. The feature will be supported in a future release. For details about IGF, see the document Developing Applications with Identity Governance Framework in the Oracle 12c documentation library.

ADF Model

Deprecated Usage of invokeAction in the Binding Editor Dialog (16245889)

The invokeAction executable has been deprecated in Oracle ADF release Oracle recommends that developer use a method activity in a task flow to call an action binding (or any backing bean method) to perform some application behavior before the page is rendered. For example, for a page used to create an object, you might have a task flow that begins with a method activity that calls the CreateInsert operation. The task flow then proceeds to the view activity for the page where the user inputs data. Modeling this behavior as discrete method call activities provides a much cleaner separation of application logic and data bindings, making applications both self-documenting and easier to maintain.

ADF Desktop Integration

Known issues related to displaying web pages using the Dialog action

  • If the end user displays a web page from a Dialog action and then allows the web app session to timeout, there may be a loss of necessary context if the server renews the session automatically. In such cases, Table.RowDownSync may not produce the expected result. (bug 9718945, bug 13440853) Workaround: enhance the web page's bean code to detect a change in the current row and cancel the dialog.

Known issues at design-time

  • Deleting cells. If the developer deletes a cell adjacent to the cell containing an ADF component and shifts that cell into the position of the deleted cell, ADFdi offers to delete the component. (bug 9737702) 

    Proxy Authentication error message after entering valid login credentials (Bug 16910021)

    Problem: "WebException: The remote server returned an error: (407) Proxy Authentication" error message after entering valid login credentials.
    Cause: The server environment is configured to enforce proxy authentication that is incompatible with ADF Desktop Integration.
    Action: Reconfigure the authentication mechanism to allow an exception for ADF Desktop Integration client requests to communicate with the Fusion web application server without authenticating through the proxy server.

ADF Faces and Data Visualization Runtime

ADF Faces Runtime

  • Browser specific bugs
    • IE9 inputComboboxListOfValues in table or treeTable - The af:inputComboboxListOfValues component will not function properly inside of table or treeTable components.
    • IE7, IE8, IE9 layout components - In some layout components, images in the af:commandImageLink component are clipped. Application Developers can fix this by setting the styleClass="AFLinkIEWorkaround" element on the af:commandImageLink tag.
    • IE7 nested table elements - If you have nested table elements and an input element with % width, the input field grows when you type into it (Oracle IE7 bug 9869651).
    • IE7 inputFile component - The af:inputFile component allows the user to type in the name of a file. This can cause problems if the file does not exist. For reasons like this, IE8 does not allow the end-user to type in the filename.
    • IE10 Select Choice component - Due to a bug in IE10, the select choice component does not open up the selection list until focusing on another UI control first then focus on the select choice component (Oracle IE10 bug 16046192).
    • Firefox 3 Access Keys - Access keys do not work properly on the af:inputFile component (Bugzilla bug 554099), and on the af:selectManyShuttle and af:selectOrderShutle components in screenreader mode (Bugzilla bug 554104). The workaround is to use tab key instead to access the component.
    • Firefox 3 Enter key in the Rich Text Editor - Pressing the Enter key in the Rich Text Editor's text field loses the selected font name because of a Firefox queryCommandValue bug (Bugzilla bug 409788).
    • Firefox 2 - The cursor is not visible on text fields in popup or table components Bugzilla bug 226933). There are several other rendering issues in Firefox 2 that are fixed in Firefox 3. Mozilla no longer supports Firefox 2, so we are unable to get any fixes for that browser from them. We recommend that if customers run into rendering issues on Firefox 2 that they move to Firefox 3.
    • Desktop Safari 3 - The af:richTextEditor component does not function properly in WYSIWYG mode (Webkit bug 7138), many keyboard shortcuts do not work properly.
    • Google Chrome - When users press Ctrl-N or Ctrl-T to launch multiple Chrome browser windows and then copy the URL to bring up pages with active data, active data doesn't work correctly (Oracle bug 8309340).
    • IE browser, Rich Text Editor - IE doesnot support links in contentEditable or designMode ,this is browser limitation , Due to this issue the hyperlinks will not work properly in RTE in IE7 , IE8, IE9.
  • Accessibility: Column Headers for Total/Subtotal Cells (6931494)
    ADF Faces users can typically produce accessible table content by specifying column headers for every column in their af:table. However, in certain complex cases, such as when the af:table contains total or subtotal rows, the cell containing the labels for these rows may be inappropriately associated with the containing column's column header. For example, assuming a column contains employee names and has the header text "Employee Name", a cell containing the text "Total" will be inappropriately identified to screen reader users as being an "Employee Name". In order to avoid confusion, such cells should not be associated with any column header. ADF Faces does not provide any mechanism for suppressing column headers for such cells.
  • Accessibility: Keyboard Selection Request Frequency (6238722)
    When interacting with an af:table, af:tree, or af:treeTable, using the up/down arrow keys to change the selection can result in a round trip to the server. ADF Faces already optimizes to reduce the number of round-trips by only sending a single request at a time, and also by dropping requests for intermediate selection states that occur while a request is outstanding. However, in some cases keyboard users may find the current behavior inefficient, since a request is sent to the server as soon as the request queue frees up. Ideally, no request would be sent until after the user has reached the item that they intend to select - ie. until after the user has paused keyboard activity for some short period of time.
  • Active Data Service (6926281)
    If Active Data Service is enabled in an application, there are certain ADS pages (/adwwls/ and adw.jspx) should not be cached. If Oracle Web Cache runs for the application, need to add cache rule to exclude pages with name of /adwwls/ or adw.jspx.
  • ADF Faces Stamped Components with MDS
    ADF Faces components do not support persisting customization changes to MDS if the component is contained inside of (anywhere in the subtree of) af:forEach or af:iterator tags. This limitation is because, while such structure results in multiple component copies in the view tree, they have a single representation in the jsp documents.
  • Application View Cache (6495920)
    The Application View Cache won't work for any page where the rendering of the component tree causes the structure of the component tree to change temporarily. Since this is often the case and the application developer has no way of telling when this will occur, USE_APPLICATION_VIEW_CACHE should never be used. It also only helps initial render performance and does not help the session size.
  • Browser specific bugs
    See the browser specific bugs listed in the Supported Platforms section.
  • Calendar Binding data type support
    Due to the lack of support in model to convert data of type java.util.Date to java.sql.Date, a runtime error will occur if java.sql.Date is specified as NDType in the calendar page definition file. Please use the supported types instead:
    • oracle.jbo.domain.Timestamp
    • oracle.jbo.domain.Date
    • java.sql.Timestamp
    • java.util.Date
  • convertDateTime may not work with pattern "MMM" on Websphere Application Server (WAS)
    On IBM JDK deployments (WAS), date patterns which contain 3 or more letters for the month, e.g. 'MMM' may fail, e.g. on locale 'zh_HK' it fails with a Javascript parse error even though the user has not modified the value. This is tracked as bug 14088506.
  • convertDateTime does not work with dateStyle="full"and locale="th_TH" or "ja_JP_JP"
    When the dateTimeConverter is used with dateStyle="full" and Thai Buddhist (th_TH) or Japanese Imperial (ja_JP_JP) locales, a Javascript error will be thrown even if the date is valid. This is tracked as bug 12861287.
  • convertNumber does not work with type="percent" and locale="tr_TR"
    When convertNumber is used with type="percent" and locale="tr_TR", a Javascript error will be thrown even if the number is valid. This is tracked as bug 13006484.
  • Dialog Framework, new browser window, and RTL Locale (12630300) - Bug 12630300 identified a layout issue with IE version 9 and greater, Microsoft SR 111072584108293. This issue is further isolated to the use of the dialog framework launching a new browser window and only when the locale is RTL. This SR is targeted for IE10 but it is unknown yet if it will make this release. As a workaround the .AFDialog-tr-enable-ie-rtl-toggle skinning property key can be used to enable a workaround. This workaround is not implicitly activated. It must be enabled in a custom skin. Consider:
    @agent ie and (version:9) { .AFDialog { -tr-enable-ie-rtl-toggle: true; } }
  • Emailable Page
    The table component has some known issues in emailable page mode.
    • The Total/Subtotal rows of the table are not bold in Outlook (8554509). The application developer would need to define the bold style directly on their outputText.
    • The detailStamp, if disclosed, does not render as disclosed in emailable page mode in both Thunderbird and Outlook (8868756).
    • columnStretching="last" does not work in emailable mode since this happens in javascript and javascript is not supported by email agents (8827678). You need to set the width attribute on the af:column components.
  • GlassFish Logging Error Message - NoClassDefFoundError: weblogic/servlet/http/AbstractAsyncServlet
    When application is deployed to GlassFish application server, user may see the following error message in server log file:
    Error in annotation processing:
    java.lang.NoClassDefFoundError: weblogic/servlet/http/AbstractAsyncServlet
    This error message can be ignored.
  • Hot Keys
    Application developers must be cautious when assigning access keys to menus. Hot keys may be intercepted by various browsers or even the operating system. One such hotkey, ALT-D, will send focus to the address bar in both IE and FireFox 2. For this hotkey, we have removed the references in our demos. But many more hotkeys may be restricted so it is a good idea to try them out on all of your supported browsers.
  • Primary Keys from Model (6894412)
    In previous releases, ADF Faces components expect applications to use primary keys on the model data objects that are pre-populated for new records and do not change with any record updates. This limitation has been removed from the current release except for the case where the affected row is not in UI range while its key is changed programatically in a backing bean.
  • Profiler File Logger The profiler file logger can be used only in a non-portal environment on FF and IE browsers with at least 1.5._06 JRE on the client box and privilege to write to the user home dir. The resulting file format is subject to change without any notice and not intended to be used with any xml parser tool. In order to use the feature, the user has to accept the certificate.
  • RichText Editor Error Messages (11686814)
    It is recommended that the application developer add a validation rule for situations where the Error Message returned by the RichText Editor would include the text contained in the RichText Editor and that text may be large enough to not be properly displayed by the browser.
  • RichText Editor on Tablet devices
    • If the rows attribute is not specified then the editable area of the RichText Editor in RichText Editing Mode will grow with the content added. Therefore, when running on tablet devices, please make sure the component is configured with the rows attribute defined.
    • Once the user clicks on the editable area the keyboard opens up. Clicking outside the editable area (such as the toolbar buttons) will then close the keyboard. In addition, the cursor position will not be retained upon clicking back on the editable area.
    • On all versions of iOS any touch event listeners added to the document are disabled when the editable area of the RTE has focus and are added back again on blur. This is due to iOS bug Therefore, if you have manually added any touch event listeners to the document, please make sure you have used the ADF API AdfAgent.addBubbleEventListener() to do so. That way your touch event listeners are removed and restored properly.
  • Skinned Icons Resize (10058868)
    Until recently there were limitations with skinning icons that -tr-rule-ref and -tr-inhibit were not supported. Further, the skin properties were not inherited from base skin for icon selectors. We fixed these limitations to make the icon selector behavior consistent with general skinning style selectors. Now that we inherit the skin properties for icons, if there were 'content' and other properties like 'width' and 'height' set, and you override just the 'content' property in your custom skin, you would inherit the 'width' and 'height' from the base skin. While this is a change in behavior, it is a change in right direction. If this behavior is not desirable, skinners can use -tr-inhibit to inhibit some properties or 'tr-inhibit: all' to inhibit all properties before overriding the 'content' property.
  • StringIndexOutOfBoundsException in (9400134) This error happens due to bug (HotSpot compiler bug in String.indexOf() using SSE4.2 instruction-set on new Intel chips). Workaround: Add this line to the JVM options: -XX:-UseSSE42Intrinsics then remove the cached CSS file, e.g., $APP_TMP_FOLDER/public/adf/styles/cache/blafplus-desktop-ezog8j-en-ltr-gecko- restart WLS, clear your browser cache and everything should be working. Please note that the bug should be fixed with jdk6.18b02 but we see it on 6.18b07
  • Trinidad app and New Window Detection (8677612)
    New Window Detection logic only works in Rich Client applications, but not in Trinidad appliations. For Trinidad applications, the following parameter should be added in web.xml to disable New Window Detection logic. {{ <context-param>
  • User Activity Monitoring and Browser Support
    • Because of a limitation in the IE userData persistence behavior, the userActivity data for previous requests may be partially or sometimes completely unavailable when accessed from pages with a different URL than was used when the page was originally saved. In IE 5 and later, data stored using IE userData persistence is accessible only to web pages within the same directory and on the same domain. This means that a webpage in a sub folder though part of the same origin cannot access the data persisted by a page in its ancestor folder (8809021). Additionally when IE userData persistence is disabled, client-side tracking of user activity data will be unavailable (it's recommended that the Oracle RUEI feature be explicitly disabled in this case).
    • In Safari when a user goes into Private Browsing mode, user activity monitoring will be disabled and as a result no user activity data will be reported. The reason for this is because the DOM sessionStorage object is unavailable as for storing any data and attempts to set a value on it throws an error (14368121).
  • User Activity Monitoring and Client-side Redirects (13610257)
    PPR requests that result in a client-side redirect now include in its resposne headers 2 new parameters - Adf-Location and Adf-Status-Code. Adf-Location points to the redirected URL as determined by the server, but the URL may change as determined by the client PPR Navigation logic. So the actual page user is redirected to might not actually be the one in Adf-Location.
  • User Specified Window Names
    In this release we start to support user specified window names. A user can launch a window and give it a name, and we will continue to use that name if it's valid. Currently the supported character set for window name is : [a-z][A-Z][0-9]_
  • InputFile component in multiple file upload mode using IE When an InputFile component configured to support multiple file upload is used with IE with Java enabled, the following settings must be set.
    • In the IE security level for the zone, the option "Include local directory path when uploading files to the server" must be enabled.
  • Supported browsers for InputFile component in multiple file upload mode Multiple file upload is supported on all release supported browser versions. However, there are a few features of InputFile in multiple upload mode which are dependent on Browser version and Java applet support.
    Browser Version Java Applet Supported Features
    Drag and Drop Progress Bar Chunked File Upload for files greater than 2GB
    IE All release supported versions Yes Yes Yes Yes
    IE All release supported versions No No No No
    FireFox All release supported versions Yes Yes Yes Yes*
    FireFox v5 and newer No Yes Yes Yes
    FireFox Older than v5 No No No No
    Chrome All release supported versions Yes Yes Yes Yes*
    Chrome v10 and newer No Yes Yes Yes
    Chrome Older than v10 No No No No
    Safari All release supported versions Yes Yes Yes Yes*
    Safari v5.1 and newer No Yes Yes No
    Safari Older than v5.1 No No No No

    *Only for files added through Drag and Drop

  • CodeEditor Limitations on iOS
    • CodeEditor does not support text selection and Copy/Paste on iOS.
  • Keyboard navigation in Table For navigation using the Enter key to work the Table must have rowHeader set.

ADF Data Visualizations General

  • The following tags are intended for future functionality and should not be used in this release: <dvt:clientLayout>, <dvt:diagram>, <dvt:diagramLink>, <dvt:diagramLinks>, <dvt:diagramNode>, <dvt:diagramNodes>, <dvt:linkAttributes>, <dvt:nodeAttributes>, <dvt:overviewWindow>, <dvt:palette>, <dvt:paletteItem>, <dvt:paletteLink>, <dvt:paletteLinkDefs>, <dvt:paletteSection>.
  • Similarly, Java classes in the following packages should not be used in this release:,

ADF Data Visualization Graph and Gauge

  • Graph and Gauge now support HTML5 output format. A new web.xml context parameter was introduced to allow application developers to use the HTML5 output format. Valid values for this parameter are HTML5 and FLASH. Applications that have this context parameter and haven't specified image format, would automatically default to HTML5. For the applications that do not have this context parameter, the default rendering for Graph and Gauge would be Flash.
  • imageFormat attribute is now deprecated. Applications are recommended to enable HTML5 using the web.xml context parameter and to remove usages of the image format attribute.
  • Application developers are advised to use the flash-player-usage parameter in adf-config.xml to disable Flash usage if needed.
  • Text in bidirectional locales sometimes does not render correctly in Flash when using Google Chrome browser. The workaround is to use HTML5 rendering for Graph and Gauge. (14512792)

ADF Data Visualization Gantt Chart

  • Label alignment does not shift when impossible to show label as defined. I.e. task with left-aligned label placed all the way to the left(8914616)
  • Issue when zoom using scroll wheel using Safari browser, CTRL-Scroll wheel is reserved for Browser font resizing (8684652)
  • Time value in tooltip of DataChangeListener incorrectly calculated (9868647)
  • Scheduling Gantt resource region sometimes displays "Warning: no row header found" (11735740)
  • When creating a RUG Gantt chart with a start time if a different year than the end time, an error is displayed when opening the jsf page in the visual editor (16851283)
  • Gantt Chart support for RTL (right to left) languages, such as Arabic or Hebrew, is only available with Internet Explorer 7, 8, and 9. (18322136)

ADF Data Visualization Hierarchy Viewer

In certain situations, configuring a Hierarchy Viewer to use same-level navigation with the levelFetchSize attribute against a BC4J data control may result in an infinite loop between the client and the server. This issue can be worked around by setting the range size of the corresponding iterator to -1 in the page definition.  (16517174)

ADF Data Visualization Pivot Table

  • In order to store edits, the PivotTable needs to be bound to a DataControl/Model that supports writeback operations. A Rowset based DataControl, like the BC4J based DataControl, is transformed into a cube and, due to the transformation, cannot support writebacks (8895660)
  • When using Internet Explorer in BIDI mode the PivotTable scrollbars can sometimes reset to their original position (8316539)
  • Leading zeros are not carried from the pivot table to exported Excel (9927815)
  • Pivot Table support for RTL (right to left) languages, such as Arabic or Hebrew, is only available with Internet Explorer 7, 8, and 9. (15948117)

ADF Data Visualization Pivot Filter Bar

JAWS tabbing through the PivotFilterBar incorrectly reads the URL (8777349)

ADF Data Visualization Timeline

  • Zoom does not work if no dvt:timelineOverview tag is specified inside dvt:timeline.  Workaround is to specify dvt:timelineOverview tag with visible attribute set to "false" to achieve the same effect (17024232)
  • Using customTimeScales attribute results in InvalidTimeScale exception (16977611)

ADF Data Visualization Thematic Map

When Thematic Map has a collapsible legend and is displayed with a skin different that Skyros, upon collapse the user is unable to expand the legend.  To avoid this issue, we recommend setting legend display to fixed. (16679659)

ADF Faces and Data Visualization Design-Time 

  • Live data preview in the DVT Graph, Gauge, and Pivot Table binding dialogs is not available during design time if the application is configured with ADF Security. (8872334)
  • Live data preview of databound components in the Create dialogs for Graphs, Gauges, and Pivot Tables is not working. (16636232)
  • When a new databound Graph is created from a Collection with a name-value pair data shape, the resulting Graph is created with <dvt:attributeFormat> child tags that are not supported for name-value pairs.  The workaround is to delete these <dvt:attributeFormat> child tags. (13529415)
  • When attempting to configure a databound Thematic Map with graduated symbol Point Markers (i.e., fixed Marker shape, color, and legend label with an Attribute Group defined to vary ScaleX, ScaleY), the validation rules for the Configure Marker dialog lead to a redundant Legend Section being generated.  The workaround is to delete the redundant Legend Section (specifically, the <dvt:legendSection> child tag whose 'source' property refers to the Marker's <dvt:attributeGroups> tag). (13851019)

Team Productivity Center

Team Productivity Center installer help button does not open the correct page.

When using Team productivity Center installer to install new or upgrade existing server, the HELP button, when clicked, does not open the correct help content. Please use the following URL instead:

ADF Essentials

ADF Essentials applications do not render DVT components on GlassFish (17436534)

When running an ADF Essentials application on GlassFish which uses DVT components, the DVT components do not render. There is a patch to address this issue available from Oracle Support. The patch can also be obtained directly from OTN.

To install the patch, follow the instructions in the patch readme. In addition, note that after applying the patch, you need to regenerate and redeploy the ADF essentials EAR and WAR archives using the deployment profile in JDeveloper.