Oracle JDeveloper Release Notes (Known Issues)

Last Updated January 30, 2015 This document lists known issues for this release. As new issues arise, they will be added to this document.  We welcome and encourage your feedback. Your input helps us make the product better. Please use the JDeveloper community discussion forum on OTN for questions and answers, as well as to let us know what you think!

General Issues

Installation JDeveloper on Mac OS (8283602)

Some additional steps are required to install JDeveloper on Mac OS beyond what is documented in the installation guide. Please refer to the installation guide ( for additional details on installing JDeveloper for Mac OS X.
1. Make Java 6 the default VM.

  • Run Java Preferences (in /Applications/Utilities/Java)
  • Move the Java SE 6 (64 Bit) to the top of the Java application versions list (General tab)
    2. Create a symbolic link for classes.jar
  • Enable root user:
    • Open the Directory Utility app from Applications - Utility
    • Ensure the settings are unlocked (click the lock if necessary)
    • Choose Edit > Enable Root User and provide the root user password.
    • Note, you can return to this same screen to disable root user after creating the symbolic link
  • Create the symbolic link: cd /SystemLibrary/Frameworks/JavaVM.framework/Versions/1.6.0/Home/
    su root
    mkdir jre
    CD jre
    mkdir lib
    CD lib
    ln -s ../../../Classes/classes.jar rt.jar
    An additional step is required to successfully run applications on Mac systems that have Java for Mac OS X 10.5 Update 4 installed (8681385):
  1. Open the jdev.conf file. The file is located in the MW_HOME/jdeveloper/jdev/bin/ directory.
  2. Add the following line to the jdev.conf file: AddVMOption

Applying Patches to Integrated WLS

When you install JDeveloper, a complete WebLogic Server environment is also installed for development, testing, and debugging purposes, also referred to as the JDeveloper Integrated WLS. In the event that it is necessary to apply patches to Integrated WLS, you can use either the SmartUpdate feature of WLS or Oracle Opatch depending on how the patch is provided from Oracle.


Unable to connect to SVN server using TLS (20015693)

JDeveloper includes SVNKIT 1.3.0 in this release which does not support TLS for making a secure connection to the Subverion server. In cases where SSL 3 has been disabled on the server and TLS is being used instead, JDeveloper will be unable to connect. There is a patch available that updates the version of SVNKIT to 1.3.8 which does have TLS support. Refer to patch number 20015693.

Database Development

Error message when you have one or more unsupported database objects in the Database Cart (15903849)

If you try to deploy unsupported objects to an Oracle Database Cloud Service connection you will see an error message. Unsupported objects are, for example, external tables, database links, materialized views, materialized view logs, synonyms, objects from a non-Oracle connection type, objects that use an unsupported datatype. For more information about the database objects that are not supported, see "Database Cloud Service Features and Implementation Considerations" which is available on Oracle Technetwork at

Goto Declaration and Find Usages for Packaged Procedures and Functions (12422139)

Usages of packaged procedures and functions from outside the package are only listed when you use Find Usages on the definition in the package spec. Usages of packaged procedures and functions from within the package body are only listed when you use Find Usages on the definition in the package body. The usages are not listed together.

Goto Declaration and Find Usages for Type methods (12422169)

Methods in Type bodies may not be correctly identified when you use Goto Declaration or Find Usages.

Creating a Database View on a Database Diagram (12334344)

When you first create a new view in a live database on a database diagram, the relational usage that the view has on a table is shown as NOT LOCATED.

The workaround is to save the diagram and either use View > Refresh, or close the diagram and reopen it, and the relational usage will be shown correctly.

Migrating .generate Files from Earlier Releases of JDeveloper (10385245)

The persistence format of .generate files changed between JDeveloper 10.1.3 and JDeveloper If you are migrating from earlier releases to JDeveloper as part of the migration to the current release of JDeveloper and you have .generate files, then you need to force any .generate files to be saved by JDeveloper in the new format.

The way to do this is to open the .generate file and make a change to it, then click OK to save the file.

Generating from Offline DB to SQL Script (12945650)

If you generate offline database objects from an offline database to a SQL script, and in the Choose Operation page you select Override Schema, an error is reported.

The workaround is to generate the SQL script without selecting Override Schema and specify a different schema by editing the generated SQL file.
Alternatively, rename the schema in the offline database before generating the script. In this case you need to check Prefix object name with schema name on the "SQL Script Options" page.


Using JDeveloper with Oracle WebLogic Server 10.3.6 (13016584)

JDeveloper is distributed with WebLogic Server 10.3.5. If you want to configure a WebLogic Server 10.3.6 domain to test an ADF application , you will need to install WebLogic Server 10.3.6 and use the 10.3.6 JRF template to add the ADF runtime libraries.

To do this:

  1. Create a new domain using the configuraiton wizard for the WebLogic Server 10.3.6 instance at wls1036_home/wlserver_10/3/common/bin.
  2. Invoke the Fusion Middleware Configuration Wizard from middleware_home/oracle/wlserver/10.3/common/bin.
  3. Extend the domain you created in step 1.
  4. Select Oracle JRF -[oracle_common], and complete the wizard.

Migrated Application Fails With Validation Problems (8822394)

If you migrate an application that contains web.xml with from JDeveloper, it may fail with validation problems when it is run on Integrated WebLogic Server.

To fix this, open web.xml in the source editor and add "/" in front of "login.html" and "error.html" in the login-config tag. For example:








Installing the Oracle Java Cloud Service SDK (13347407)

If you are deploying an application to Oracle Public Cloud you first need to download and install the Oracle Java Cloud Service SDK.

Download the Oracle Java Cloud Service SDK from The downloaded SDK is a ZIP file which contains a top-level directory oracle-javacloud-sdk-X.x.x. If you unzip the file into the default location $MW_HOME/jdeveloper/cloud the Oracle Java Cloud Service SDK is now available for you to use. If you unzip into a different location, you must set that location in the Oracle Public Cloud page of the Preferences dialog.

Configuring WebSphere Application Server to Allow Reuse of Query Result Sets

WebSphere Application Server closes shared database connections between application generated requests. You need to set two properties in WebSphere to allow reuse of result sets.

Use the WebSphere Application Server administrative console to set the non-transactional datasource and DisableMultiThreadedServletConnectionMgmt properties.

  1. Start WebSphere Application Server administrative console.
  2. Navigate to Data sources > DB2 Universal JDBC Driver XA DataSource > WebSphere Application Server data source properties and set Non-transactional data source to enabled.
  3. Save the configuration.
  4. Navigate to Application servers > server_name > Web Container > Custom Properties and set DisableMultiThreadedServletConnectionMgmt to true.
  5. Save the configuration.
  6. Restart WebSphere Application Server.

Setting these two properties will enable your deployed application to reuse result sets across requests.

From JDK 7 Update 21 onwards, applets will no longer run under default security settings (16432858)

If you are using Java Web Start (JNLP) files, starting with JDK 7 Update 21, applets will no longer run under the default security settings unless the applet is signed by a trusted certificate authority. For more details, refer to the Java web site at

 Ojdeploy Behavior Change When Using -nodependencies (16073770)

In earlier versions, the -nodependencies flag prevented deployment from following Project to Project dependencies, now this flag also prevents Profile to Project dependencies. Ojdeploy will only compile and package the targeted project's contents.

This also means that EAR profiles, which use profile dependencies to assemble other Java EE modules, will not deploy those automatically. Each composed module must be individually packaged using ojdeploy before the EAR is deployed.

Web Services Development

Some combinations of features can result in JDeveloper running our of PerGen space (13242177)

You might see the error "java.lang.OutOfMemoryError: PermGen space" when running JDeveloper, if you see this try increasing the -XX:MaxPermSize= value in jdeveloper/jdev/bin/jdev.conf to 288M or greater to see if this resolves the problem.

Http Analyzer doesn't support 2009 WADL revision (12956438)

If you are running JDeveloper against WebLogic service 10.3.6 with the Jersey 1.9 libraries you will find that the URL highlighting doesn't work in the analyser when looking at '2009 version of the WADL as generated by the new version of Jersey. There is no fix for this problem; but it is resolved in

Ignore warning message displayed when upgrading JAX-RPC web service in JDeveloper (8912681)

When upgrading a JAX-RPC Web service developed using JDeveloper from Oracle Containers for J2EE (OC4J) to Oracle WebLogic Server 10.3.x, the following warning may be displayed. This warning is displayed when the OC4J Web service contains whitespace or carriage return characters within the code. This warning can be ignored.

WARNING: A Text node was set to a value that is all whitespace. The DOM will be out of sync with the Text Buffer. The Text Node on reparse will also be removed from the DOM. 

Avoid creating multiple top down web services in the same project/package (7165531)

Unless they are 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.

Manually edit the header details if invoking WLS stateful (conversational) web services from HTTP Analyzer (7388843)

When calling conversational web services from HTTP Analyzer, the request message headers for the 'continue' methods need to be manually updated with the conversation id that is specific to that particular conversation. This value is available from the response SOAP message of the method that starts the conversation.

From the response message of the conversation start method, copy the xml tags similar to the one below:

<conv:ContinueHeader xmlns:conv="">



From the HTTP Content tab in HTTP Analyzer, insert the above tags within the header element of the SOAP request message, as below:

<env:Envelope xmlns:env="">

<!- other header elements-->

<conv:ContinueHeader xmlns:conv="">



<!- message data details ->


Services migrated from a previous JDeveloper release are not guaranteed to deploy and run in WLS

Because of the OC4J proprietary nature of some of the properties set on web services that were created with previous JDeveloper releases (which supported OC4J), it is likely that there will be problems when attempting to deploy and run such services on WLS (including the integrated WLS that is bound with JDeveloper). Known problems include JAX_RPC services that have annotations, stateful services, DIME encoding, OWSM Policy (both 10.1.3 and 11 styles including WS-Security and WS-Reliability).

Cannot deploy and run JAX-RPC with bare array types as method parameters (7493019)

When using JAX-RPC web services deployed to weblogic using the generators in JDeveloper you may have
trouble with method signatures that contain "bare" array types.

For example: public class Hello

These will either not deploy or when deployed will not work properly with errors complaining about mapping issues. There are a few workarounds for this problem:

  • *# Only do wrapped parameters, when starting from a java class Create a bean object that contains all the properties. When creating the web service make sure you select Document/Literal rather than Document/Wrapped to prevent double wrapping.
    1. Make sure you don't allow properties to be unwrapped when doing "top down" On the mapping options page when generating a Java web service from a WSDL make sure you uncheck the "Unwrap Wrapped parameters" box on the "Specify Default Mapping Options" page of the wizard.
    2. Use the weblogic jwsc ant task The ant task will generate a working service from the bare list types but the schema for the WSDL will generate synthetic Java schema types which may not be what the user wants.

JAX RPC stateful service: JAX WS client is throwing exception (7533170)

It is not possible to successfully invoke a JAX-RPC style conversational (stateful) web service deployed in weblogic server from a JAX-WS style proxy client. The design time JAX-WS proxy creation does not currently warn the user if the supplied WSDL document contains conversational behavior advertisement. Even though the tool leads to a successful generation of JAX-WS client artifacts, invoking the service from this client results in a SOAPFaultException. Only the conversation 'start' methods will get executed successfully. Invoking any other conversational methods after a conversation 'start' method will result in error.

The workaround is to use a JAX-RPC style proxy client to call a stateful service deployed in the weblogic server.

JAX-WS async client for a 10.1.3 BPEL process will not run by default (7422130)

The BPEL server included in 10.1.3 SOA only knows how to use the '2003 draft version of the WS-Addressing specification. The JAX-WS async client will be default generate a client that by modifying the WS_ADDR_VER constants to support either the final '2005 or the member submission '2004 version of the specification. To support the '2003 version the user will need to make some minor modification to the code in order to invoke the process properly.

In the callback handler you need fix the code that requests the relatesToHeader as shown here:
// HeaderList ...
//Header relatesToheader = headerList.get(WS_ADDR_VER.relatesToTag, true);
//String relatesToMessageId = ralatesToheader.getStringContent();
String relatesToMessageId = RelatesTo.getValue();

This uses the header which get automatically bound to a method parameter. Now the BPEL service explicitly defines both the ReplyTo and MessageID headers in the WSDL so the default proxy generator will map these to method parameters. Assuming that you accept this default you need to pass both the replyTo address and the message ID in as parameters to the method rather than as header as you will see in the generated code. The only exception for this is the WS-Addressing action header which if it is required should be set using the '2003 namespace. Here is an example that invokes a loan process that has the required edits.

americanLoan = new AmericanLoan();
LoanService loanService = americanLoan.getLoanServicePort();

// prepare Message Id

AttributedURI messageId = new AttributedURI();
messageId.setValue( "uuid:" + UUID.randomUUID() );

// prepare ReplyTo

AttributedURI address = new AttributedURI();
EndpointReferenceType replyTo = new EndpointReferenceType();
replyTo.setAddress( address );

// prepare action header

WSBindingProvider wsbp = (WSBindingProvider)loanService;
new StringHeader(
new QName( "", "Action" ),
"" ));

// Prepare payload

LoanApplicationType payload = ...

// Invoke service with replyTo and messageID parameter
loanService.initiate(lt, replyTo, messageId);

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 with ADFdi List of Values components

  • Empty forms (bug 8651633, bug 8651645)
    An Excel form cannot be configured to use ADF List of Values components which use model-driven list bindings if the form's bound iterator is expected to contain zero rows. Workaround: configure the ADF List of Values component to use a "dynamic" list binding instead.

Known Issues with Excel 2010

  • Unexpected errors occur with Excel's Protected View feature (bug 13397830, bug 14325303)
    ADFdi is not compatible with the "Protected View" feature Microsoft introduced in Excel 2010. Protected View can be enabled for a variety of reasons. If an integrated workbook is opened in Protected View, ADFdi will report unexpected errors. See the following link for details and work-arounds:

Known issues involving the Read-only Table Component

The following known issues may be encountered when working with the ADF Read-only Table Component. To avoid these issues, consider using a the ADF Table component in a read-only configuration.

  • Server-side row set can be Positioned on Wrong Row When DoubleClickActionSet Invoked on ADF Read-only Table Component (bug 8272219)
    An ADF Read-only Table component only caches the original row set index in an integrated Excel workbook. Invoking a DoubleClickActionSet on an ADF Read-only Table component results in an attempt to position the server-side row using the cached row index.
    If the server-side row set changed in between the time the ADF Read-only Table component caches the original row set index and the DoubleClickActionSet is invoked, the server-side can be positioned on the wrong row.

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.

Migrating from previous releases of Oracle ADF 11g

  • Automatic client upgrade: version of ADFdi requires Microsoft .NET and VSTO version 4. The automatic client update does not handle the change in prerequisites correctly and fails instead. Solution: uninstall the client (from Windows' Add/Remove Programs control panel) and re-install using ADFdi's setup.exe program that installs the new prerequisites.
  • ADFdi Shared Libraries. Starting in, ADFdi server components are delivered as part of the "JRF" and no longer need to be included explicitly in your web application. If you are creating new WLS domains using, the ADFdi shared libraries are included automatically. However, if you have already created your WLS domain using, you will need to perform a special step to upgrade that domain. For example, running the WLST command "updateJRF()". See 'Updating Fusion Middleware Shared Libraries' in the 'Oracle Fusion Middleware Patching Guide': link: 
  • Cannot upload saved changes from workbook after migration to (bug 10358830)
    Solution: Prior to upgrading from to, be sure to upload or discard any pending changes in saved workbooks. After migration, be sure to re-download any data in saved workbooks.
  • Workbook Migration
    If you wish to use integrated workbooks created using or earlier with ADFdi, you will have to perform one or more migration steps. The migration can be performed at design-time and also on published runtime workbooks. It is preferable to convert design-time workbooks and re-publish so that end users do not have to experience the migration.
    In general, you cannot have two versions of ADFdi installed on the same computer. There is an exception in this case: you can leave installed while migrating workbooks to If you do so, you will avoid seeing several errors. However, if you have already uninstalled the old version, you will see 1 or 2 errors during the migration of each workbook as it tries to access the old version. These errors can be dismissed and ignored. Assuming that you are migrating workbooks at design-time, the steps are:
    1. Install the new ADFdi client
    2. Create a backup copy of the design-time version of your workbook
    3. Open the design-time version of your workbook
    4. Dismiss any error dialogs if the old client has been uninstalled
    5. When prompted to migrate, click "Yes"
    6. Test your workbook: review/adjust the column widths of your table's Changed and Flagged columns; review the runtime ribbon tab contents; adjust any labels as desired.
    7. Publish your workbook
    8. Repeat this process for each integrated workbook in your application
      Note: a migrated workbook can no longer be used with the old client.

Versions of Microsoft .NET Framework

Microsoft has announced that it will end support for .NET 4 (on Windows 7 and Windows 8) starting in January 2016. Microsoft recommends upgrading to version 4.5.2.


ADF Desktop Integration is compatible with .NET 4.5.2. Users may install it at any time. Future versions of ADF Desktop Integration may check for and install this version of the Microsoft .NET Framework.

ADF Faces and Data Visualization

Here is an exemple: 

<af:table value="#{bindings.EmpView1.collectionModel}" var="row"
... partialTriggers="it1">
<af:column sortProperty="Empno" sortable="true"
<af:inputText value="#{row.bindings.Empno.inputValue}"
... autoSubmit="true" id="it1">
<f:validator binding="#{row.bindings.Empno.validator}"/>
<af:convertNumber groupingUsed="false"
<af:column sortProperty="Deptno" sortable="true"
<af:selectOneChoice value="#{row.bindings.Deptno.inputValue}"
<f:selectItems value="#{row.bindings.Deptno.items}" id="si1"/>

This is tracked via ER 6894412.

  • Application View Cache 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. This is tracked via bug 6495920.
  • Trinidad app and New Window Detection 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>

This is tracked via ER 8677612.

  • 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. The application developer would need to define the bold style directly on their outputText. This is tracked via 8554509.
    • The detailStamp, if disclosed, does not render as disclosed in emailable page mode in both Thunderbird and Outlook. This is tracked via 8868756.
    • columnStretching="last" does not work in emailable mode since this happens in javascript and javascript is not supported by email agents. You need to set the width attribute on the af:column components. This is tracked via 8827678.
  • ADF Faces Repeated Components by af:forEach and af:iterator ADF Faces components do not support persisting customization changes if the component is contained inside of (anywhere in the subtree of) af:forEach or af:iterator. However, if the repeating component and the repeated component are located across document, for example, in different jsff or jspx files, then we can't detect this case and will allow the customization persistence.
  • 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 for storing any data and attempts to set a value on it throws an error (14368121).
  • Accessility: Column Headers for Total/Subtotal Cells 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. Bug 6931494 has been logged to track this issue.
  • Accessibility: Keyboard Selection Request Frequency 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. Bug 6238722 has been logged to track this issue.
  • Accessibility: Read-Only Input Components Currently read-only input components, such as af:inputText, are rendered by ADF Faces as plain text. As such, there is a loss of information that may be meaningful to screen reader users - ie. screen reader users have no way to determine that the text in question corresponds to a input control. In addition, since plain text content is not included in the tab navigation order, screen reader users may fail to recognize that this read-only content is present on the page. Bug 5889673 has been logged to track this issue.
  • UI Components State Sync When Sharing The Same Iterator Binding When there are multiple components share the same iterator binding in one page, the application needs to use partialTriggers to sync up UI states. One example is a form and a table based on the same iterator binding, the table's partialTriggers needs to point to the form's navigation buttons, for table selection to sync with form.
  • Multibyte Character Set Page Name: not supported for WebSphere Application Server Due to WAS's specific implementation of HttpServletResponse class, server side redirect for UTF-8 encoded URL with MBCS characters does not work correctly. Because of this, when you access a page with multibyte character set name, you may get Http Error 404, or "Failed to find resource" error.
  • Resource URL Session ID Rewriting In some scenarios a session id may be inserted into URLs for ADF Faces resources such as JavaScript libraries, style sheets and images. This can happen when cookies are disabled in the user's browser or the first time that a user visits an ADF Faces application, at which point the application server does not yet know whether cookies are enabled. While this does not impact functionality, it can result in a small performance hit, since the presence of the session id prevents previously cached copies of resources from being used. In cases where the application requires the use of cookies, it is possible to avoid session id URL rewriting by configuring the application server to always use cookies for session id management. For example, Oracle WebLogic Server allows session id url rewriting to be controlled by the <url-rewriting-enabled> element in the weblogic.xml file.
  • 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
  • Dialog Framework, new browser window, and RTL Locale - 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; } }
  • Using HTML 5 features in Internet Explorer 9 Unlike most browsers supporting HTML 5 features, Internet Explorer 9 requires the presence of the HTML 5 DOCTYPE to enable these features. Unfortunately, ADF Faces currently generates Internet Explorer content in almost standards mode. Changing to the HTML 5 DOCTYPE without changing the way some of the DOM is generated would result in layout changes. We are working on addressing this issue.
  • 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.
  • Client NumberConverter does not work with tr_TR locale and type=percent
    In Turkish (tr_TR) locale, numberConverters with type=percent do not allow users to enter a number, but will throw a Javascript error even if the input is valid. This is tracked as bug 13006484.
  • Client DateTimeConverter does not work with dateStyle=full and locales th_TH or ja_JP_JP
    When the dateTimeConverter is used with dateStyle=full or locale=th_TH or ja_JP_JP, there will be a Javascript error thrown even though the date is valid. This is tracked as bug 12861287
  • No Oracle-hosted resources for emailable attachments (16546053) Oracle has decided to not publicly host ADF resource files on Oracle-owned servers for the purpose of supporting ADF faces content in email attachments. This information will be removed from the documentation in a subsequent update.
  • 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.
    • If the InputFile component is in a popup then in the Java Control Panel under Advanced->Java Plug-in, the option "Enable the Next Generation Java-Plugin" must be disabled.

ADF Data Visualization Components

ADF DVT Graph and Gauge

  • Graph and Gauge now support HTML5 output format. A new web.xml context parameter was introduced to change the default output format to HTML5. This context parameter,, will automatically be added to new applications. Applications that have this context parameter and haven't specified image format, would automatically default to HTML5. Valid values are HTML5 and FLASH. For the applications that do not have this context parameter, the default rendering for Graph and Gauge would be Flash.
  • Firefox does not print Flash content, which is the default imageFormat for DVT Graph and Gauge. HTML5 is recommended on all modern browsers (6904435, 6016950)
  • If using Internet Explorer 9, the users are advised to use HTML5.

ADF DVT 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)
  • After editing a cell then sorting, column sorts on original value, not new value. (8742733)
  • Sorting in PivotTable blows away existing sorts. (8998375)
  • Pivot with keyboard can interfere with some graphics cards. (9020333)
  • User resizes are sometimes forgotten. (9047467)
  • Ability to make selections lost after pivot to PivotFilterBar. (9012546)
  • af:convertNumber and af:convertDateTime do not work when used in a Pivot Table header cell. Currently there is no workaround, as the value is already formatted into a string and therefore not a number which can be converted. (9475191)
  • Unable to use PivotTable sizingManager attribute declaratively. (11797618)
  • NullPointerException is sometimes thrown when creating a printable page with Pivot Table. (10629477)
  • Pivot Table does not have touch gesture support for row/column resizing on iOS. (9931714)
  • Double-click particular cells does not make the cell editable after a short scroll that causes data fetch.  The workaround is to navigate to the cell using tab/enter key. (16272505)
  • ValueChangeEvent from input stamp returns incorrect old value after the first time it is fired if application added other cells as partial target in ValueChangeListener the first time. (16100377)
  • Cell within Pivot Table not refresh when partial page refresh is done on return from a task flow. (10629477)
  • 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 DVT Pivot Filter Bar

  • JAWS tabbing through the PivotFilterBar incorrectly reads the URL. (8777349)
  • Arrowing during keyboard pivoting should be reversed for BiDi cases. (9002516)
  • The user cannot pivot items via the keyboard between the PivotTable and the PivotFilterBar. (8777330)
  • ADF Table and other views may be refreshed when PivotTable with PivotFilterBar is updated. (8940695)
  • PivotFilterBar attributes: visible, persist, dontPersist and shortDesc cause compile errors in the Jspx. The wrokaround is to use a backing bean instead to set these properties. (8914128)
  • Keyboard pivoting from PivotTable to PivotFilterBar component not working, vice versa works. The workaround is to use drag and drop operation. (8917681)
  • Export of PivotTable data to Excel when stamping is used ends up with duplicated values in the cells. (9672617)
  • Leading zeros are not carried from the pivot table to exported Excel. (9927815)

ADF DVT Gantt Chart

  • Label alignment does not shift when impossible to show label as defined. For example, a task with left-aligned label is 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)
  • Rollover text can appear beneath the chart right-mouse menu. (9027856)
  • Tag documentation for the project gantt and initialDateFocus is incorrect. (9026200)
  • Some debug messages appear in console when creating a Project Gantt. (8862734)
  • Regions in popup window are not getting painted properly when launched from Gantt. (9685840)
  • NullPointerException is sometimes thrown when collapsing rows in Project Gantt. (9083323)
  • SchedulingGantt: NullPointerException sometimes gets thrown on data change event (9432601)
  • Time value in tooltip of DataChangeListener is incorrectly calculated. (9868647)
  • Scheduling Gantt DT design-time view in JDeveloper gets converted into the tag-boxes view when a startTime and/or endTime are set from a backing bean. (10635436)
  • Scheduling Gantt region has "no row header found". (11735740)
  • Scheduling Gantt: snap to operation leaves a couple of pixels between tasks. (11901244)
  • Project Gantt does not have touch gesture support for linking tasks on iOS. (9931735)
  • Custom toolbar buttons disappeared after zoom actions.  Workaround is to refresh the Gantt. (14077019)
  • 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 DVT Timeline
  • Timeline could become unresponsive if the initial start and end time fits into the page without scrolling and user then zooms to a scale that causes the timeline to be extremely wide. Workaround is to specify an end time such that the timeline is wider than the viewport. (16080267)
  • An error message is displayed at design time if summary attribute is specified on the dvt:timeline tag. Workaround is to use the setSummary method on UITimeline instead. (15902974)
  • TimelineOverview is not re-sized when placed inside a stretchable container and the user increased the horizontal size of the container. (14532594)

ADF DVT Databinding and Design Time

  • When editing DVT Graph tags in the Source Editor and then using a custom button in the Property Inspector to configure a new child tag, the developer may encounter an exception. If that occurs, switch to the Visual Editor when using the Property Inspector to configure a child tag. (8965391)
  • In Step 2 of the DVT Pivot Table Binding Wizard, developers can specify an alternate attribute for attribute value labels to be rendered in the resulting Pivot Table header at runtime. However, in Step 3, if the Binding is configured for Insert Drilling, then it is possible that the specification of that alternate attribute will be discarded. If you encounter this scenario, you can use the following workaround:
    1. Edit the corresponding PageDef source;
    2. Find the corresponding element in thesection of the Pivot Table binding;
    3. Update the 'label' attribute of that element to the correct alternate attribute name. (8607695)
  • Changes made to an existing <dvt:search> child of a <dvt:hierarchyViewer> tag through the dialog are sometimes ignored. As a workaround, the developer can delete the <dvt:search> element through the Structure Pane, and then recreate it. (8926518)
  • The Component Gallery for DVT Hierarchy Viewer does not include the 'Circle' layout type. You can choose this option in the Property Inspector after the tag is created on the page. (8862266)
  • 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)
  • When creating a Pie Graph, mapping one or more Attributes to 'Slices' before mapping a numeric Attribute to 'Pie' can cause the Attribute Labels table to be incorrectly updated. The workaround is to set the 'Pie' numeric Attribute first, before mapping additional Attributes to the 'Slices'. (9708226)
false ,,,,,,,,,,,,,,,,