Oracle JDeveloper 11g and Oracle Application Development Framework (ADF) 11g

Known Issues for JDeveloper and ADF 11g 11.1.1.6.0

Last updated: November 27, 2012

Content

Introduction

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!

Important Note: After the initial release of 11.1.1.6.0 in February 2012, we have since updated the release to enable working with Oracle Cloud. These are JDeveloper IDE changes only and do not affect the ADF runtime installation or deployed applications. To confirm which version of the 11.1.1.6.0 release you have, choose Help > About from the JDeveloper main menu. The full version information is displayed in the About box:

  • Build JDEVADF_11.1.1.6.0_GENERIC_111205.1733.6192.1: Initial 11.1.1.6.0 release with limited Oracle Cloud Early Access support (Feb, 2012)
  • Build JDEVADF_11.1.1.6.0CLOUD_GENERIC_121118.1600.6229: Updated 11.1.1.6.0 release with full Cloud support (Nov, 2012)

Installation

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

Installing 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 (http://download.oracle.com/docs/cd/E17904_01/install.1111/e13666/toc.htm) 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 -Djava.io.tmpdir=/var/tmp

Migration

VPN connection with JDeveloper and JDK 1.7

There is an issue with JDK7 using the IPv6 as the default whereas VPN on Windows requires IPv4. If attempting to make a connection using VPN, Jdeveloper and JDK 1.7 and you receive an error: IO Error: The Network Adapter could not establish the connection on a connection that works using jdk 1.6 edit the jdev.conf file and add: AddVMOption -Djava.net.preferIPv4Stack=true

Same issue can apply to the WLS server on Windows. For an external domain to run in jdk1.7 you can edit the setDomainEnv file for the domain: Set the JAVA_HOME to jdk1.7 home.

Scroll down to the set EXTRA_JAVA_PROPERTIES section and include in the list: -Djava.net.preferIPv4Stack=true

XML Tools

java.lang.illegalstateexception at JDeveloper startup (11887639)

When starting JDeveloper for the first time after installation, the XSLT file design time features like running and debugging do not work and exhibits this message:

java.lang.IllegalStateException



Exception firing mainWindowOpened to oracle.jdevimpl.runner.xslt.XSLTRunnerAddin@46b9979b
java.lang.IllegalStateException: getInstance was called while _instance was null

Workaround is to restart JDeveloper.

xslt debugger locks up (11670054)

Sometimes JDeveloper locks up while debugging an XSLT.





"AWT-EventQueue-1" prio=6 waiting
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
com.sun.tools.jdi.TargetVM.waitForReply(TargetVM.java:281)

com.sun.tools.jdi.VirtualMachineImpl.waitForTargetReply(VirtualMachineImpl.java:1015)
com.sun.tools.jdi.PacketStream.waitForReply(PacketStream.java:51)
com.sun.tools.jdi.JDWP$StackFrame$GetValues.waitForReply(JDWP.java:6967)
com.sun.tools.jdi.StackFrameImpl.getValues(StackFrameImpl.java:218)
com.sun.tools.jdi.StackFrameImpl.getValue(StackFrameImpl.java:185)

oracle.jdevimpl.debugger.jdi.DebugJDIVariableInfo.getLocalVariableValue(DebugJDIVariableInfo.java:137)

oracle.jdevimpl.debugger.jdi.DebugJDIVariableInfo.getDataInfo(DebugJDIVariableInfo.java:223)
oracle.jdevimpl.runner.debug.DataItem.setInfo(DataItem.java:179)
oracle.jdevimpl.runner.debug.DataItem.(DataItem.java:137)
oracle.jdevimpl.runner.debug.DataItem.(DataItem.java:128)
oracle.jdevimpl.runner.debug.LocalsController.addDataItems(LocalsController.java:504)

Workaround is to restart JDeveloper and remove the break point at which the deadlock happened.

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.

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 11.1.1.4.0. If you are migrating from earlier releases to JDeveloper 11.1.1.4.0 as part of the migration to JDeveloper 11.1.2.0.0 and you have .generate files, then you need to force any .generate files to be saved by JDeveloper 11.1.1.4.0 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.

Deployment

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 - 11.1.1.0[oracle_common], and complete the wizard.

Migrated 10.1.3.5 Application Fails With Validation Problems (8822394)

If you migrate an application that contains web.xml with from JDeveloper 10.1.3.5, 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:




<login-config>
    <auth-method>FORM</auth-method>
        <form-login-config>
          <form-login-page>/login.html</form-login-page>
            <form-error-page>/error.html</form-error-page>
            </form-login-config>
         </login-config>

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 http://cloud.oracle.com. 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.

Creating an Oracle Public Cloud Connection (13576896)

In the Connection page of the Create Application Server Connection wizard, enter details of your Identity Domain in the field "Service Group".

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.

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 11.1.2.1.0.

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="http://www.openuri.org/2002/04/soap/conversation/">
<conv:conversationID>uuid:701f9f3d434bfc98:-3f39a0ef:11c4b649fd4:-7fff</conv:conversationID>
</conv:ContinueHeader>

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="http://schemas.xmlsoap.org/soap/envelope/">
 <env:Header>
<!- other header elements-->
    
<conv:ContinueHeader xmlns:conv="http://www.openuri.org/2002/04/soap/conversation/">
 <conv:conversationID>uuid:701f9f3d434bfc98:-3f39a0ef:11c4b649fd4:-7fff</conv:conversationID>
 </conv:ContinueHeader>

</env:Header>
<env:Body>
<!- message data details ->
</env:Body>
</env:Envelope>

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:

  1. 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.
  2. 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.
  3. 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();
address.setValue("http://x.x.x.x:7101/Application23-Project1-context-root/LoanServiceCallbackPort");
EndpointReferenceType replyTo = new EndpointReferenceType();
replyTo.setAddress( address );

// prepare action header

WSBindingProvider wsbp = (WSBindingProvider)loanService;
wsbp.setOutboundHeaders(
new StringHeader(
new QName( "http://schemas.xmlsoap.org/ws/2003/03/addressing", "Action" ),
"http://services.otn.com/LoanService/initiateRequest" ));

// Prepare payload

LoanApplicationType payload = ...

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

Team Productivity Center Issues

Users cannot connect to Bugzilla with @ in user ID

Users of the Oracle Team Productivity Center connector to the Bugzilla repository have reported being unable to connect to Bugzilla with user IDs that contain the @ character (for example, email addresses such as myusername@mydomain.com). This has been determined to be due to two missing modules in the Bugzilla installation: SOAP-Lite and Test-Taint.

SOAP-Lite and Test-Taint are responsible for enabling the XML-RPC interface, allowing third-party tools to connect to Bugzilla. During installation of the Bugzilla server, the installer mentions that these modules (although optional) are required to enable the XML-RPC interface. However, some Bugzilla administrators might decide not to install these unless required, as they might raise a security issue.

Beginning with the 11.1.2.0.0 release, Oracle Team Productivity Center's Bugzilla connector no longer uses XML-RPC for Bugzilla access. However, releases prior to 11.1.2.0.0 require the installation of Bugzilla modules SOAP-Lite and Test-Taint during Bugzilla server installation.

ADF Desktop Integration (ADFdi)

Excel Validation and ADF Table Components (7509432)

Given an ADFdi Table component with Excel "Data Validation" rules applied to one or more columns: if the user downloads data and then inserts new rows just under the header row, the new rows do not have the Excel Data Validation. Additionally, if the workbook developer performs the same set of steps in test mode and then returns to the designer, the data validation rules are lost altogether.

Workaround: Do not insert rows just under the column headers. Instead, insert new rows anywhere in the middle or at the end of the table.

Known Limitations on changing ADFdi components at runtime (6196783, 6032482, 6161839)

  • Moving a Column in a Runtime ADF Read-only Table Component (bug 6196783)

    If the user of the worksheet containing a Read-only Table component uses Excel's cut-and-insert operations to move a column to be the left-most column of the table, an exception occurs on the next download. To resolve the situation, the user should close the workbook without saving the changes.

  • Change Tracking After Moving a Column to the End of an ADF Table Component (bug 6032482)

    Change tracking is disabled if an end user moves a column to the end of an ADF Table component at runtime. Subsequent edits to cells in the moved column do not mark the row as changed.

  • Deleting an Integrated Excel Worksheet at Runtime (bug 6161839)

    Oracle ADF Desktop Integration does not support the deletion of integrated worksheets at runtime. If the user deletes an integrated worksheet, un-handled exceptions will occur. Workaround is to close the workbook without saving any changes.

Unexpected exception when using Excel filters in test mode (7134292)

Unexpected Excel exception when returning from test mode to design-time mode if Excel filtering

is applied to a table.

Steps:

  1. Create a workbook with a table
  2. Click the run button to enter test mode
  3. Select the header row of the table
  4. Enable Excel filtering ("Sort & Filter" in the Home tab)
  5. Use Excel filter to display a subset of the rows in the table
  6. Click the Stop button to return to design-time mode

At this point, an unexpected exception occurs.

Workaround: dismiss the error dialog and remove the filter from the table.

Then click the Stop button again to return to design-time mode.

Excel Context Menus Do Not Hide/show ADFdi controls as expected (7511508)

Microsoft Excel does not invoke the "before right click" event when a user invokes a context menu from a keyboard. Users should use either the keyboard or the mouse's right-click button to invoke a cell's context menu. Do not use both in the same user session. This behavior occurs at design time and runtime in integrated Excel workbooks.

Using a variableUsage Element Causes Null Pointer Exception in ADFdi Remote Servlet (6377073)

ADFdi does not support variables in the page definition declared with the syntax of variableUsage.

If the developer creates variableUsage in the ADFdi-related page definition, it will produce NullPointerExceptions

in the server at runtime.

Workaround is to create variables instead using the <variable> element in the page definition.

Known issues related to displaying web pages using the Dialog action (11072858)

  • ADFdi does not support using ADF task flows from ADFdi Dialog actions (bug 11072858)

Known issues with the design-time property inspector and expression builder features (6314302, 7269921)

The property inspector and expression builder features in the ADFdi Designer are driven off of the saved component metadata. As a result, there are some known issues when dealing with new objects or values. In each case, the workaround is to save the object and then re-open.

Sample issues:

  • New components in the expression builder (bug 6314302) - An expression builder invoked from a newly-inserted ADF table-type component's property that supports EL expressions does not display the newly-inserted ADF table-type component in the Components node of the expression builder.
  • Cannot select UniqueAttribute for a new Table (bug 7269921) - An error message appears requesting that you first specify a value for the ADF Table component's TreeID property when you attempt to set a value for a newly-inserted ADF Table component's UniqueAttribute property. This error message appears even though a value is set for the TreeID property.

Known issues with design-time collection editors (8254551)

  • At design-time, some property inspectors provide access to "collection editors" (bug 8254551)

    For example, the Workbook properties include "Branding Items". The items can be edited in a pop-up collection editor. When making changes to existing items via this collection editor and then pressing the Cancel button, the changes to the collection are not canceled as expected. Workaround is to cancel the parent property editor to cancel the undesirable changes from the collection editor.

Known issues with ADFdi List of Values components (8575731, 8651633, 8651645)

  • Empty forms (8651633, 8651645)

    An Excel form cannot be configured to use model-driven list bindings if the form's bound iterator is expected to contain zero rows. Workaround is to configure the Excel form to use a "dynamic" list binding instead.

Known Issues with SSL (7117108, 9536914)

  • Integrated Excel Workbooks and HTTPS (bug 7117108) - Attempts to connect to a web application from an integrated Excel workbook over HTTPS result in an error if the certificate is not present on the client machine.

    Error text:

    ADFDI-00134: An attempt to connect to the web application has failed.

    Solution: Navigate to a web page from the same application using Internet Explorer. This action will install the certificate locally. Subsequent attempts to use the integrated workbook will succeed.

  • Login dialog flashes briefly for web app w/no authentication but using https (bug 9536914)

    If your web application is configured to use SSL/HTTPS, but does not use authentication, the login dialog will appear briefly when the workbook establishes a connection and then close again in order to recognize the certificate.

Known Issues with Excel 2010 (13397830)

  • Unexpected errors occur with Excel's Protected View feature (bug 13397830)

    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: http://office.microsoft.com/en-us/excel-help/what-is-protected-view-HA010355931.aspx

Known issues involving the Read-only Table Component (8272219)

The following known issues may be encountered when working with the ADF Read-only Table Component. To avoid these issues, consider using 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 (9737702)

  • Deleting cells (9737702) - 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.

Migrating from previous releases of Oracle ADF 11g (10358830)

  • ADFdi Shared Libraries. Starting in 11.1.1.4.0, 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 11.1.1.6.0, the ADFdi shared libraries are included automatically. However, if you have already created your WLS domain using 11.1.1.3.0, you will need to perform a special step to upgrade that domain. For example, running the WLST command "updateJRF()".
  • Cannot upload saved changes from 11.1.1.3.0 workbook after migration to 11.1.1.6.0 (bug 10358830)

    Solution: Prior to upgrading from 11.1.1.3.0 to 11.1.1.6.0, 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 11.1.1.3.0 or earlier with ADFdi 11.1.1.6.0, 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 11.1.1.3.0 installed while migrating workbooks to 11.1.1.6.0. 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

  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.

ADF Faces and Data Visualization

NLS issues with JDK 1.6-only locales (6859992)

Date and number formatting (convertDateTime, inputDate, etc.) do not work with the 17 new locales added in JDK1.6. All locales supported in JDK 1.5 do not have this issue.

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 directory. 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.

StringIndexOutOfBoundsException in org.apache.myfaces.trinidadinternal.style.util.CSSGenerationUtils (9400134)

This happens due to this HotSpot compiler bug (#6875866 ) in String.indexOf() using the SSE4.2 instruction-set on new Intel chips. (9400134). The workaround is:

  1. Add this line to the JVM options: -XX:-UseSSE42Intrinsics
  2. remove the cached CSS file, (e.g. $APP_TMP_FOLDER/public/adf/styles/cache/blafplus-desktop-ezog8j-en-ltr-gecko) -1.9.1.8-cmp.css.
  3. Restart WLS
  4. Clear your browser cache

Note: The bug should be fixed with JDK 6.18b02, but we see it on 6.18b07

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.

Active data service (6926281)

  • If Active Data Service is enabled in an application, there are certain ADS pages (/adwwls/wls.ads and adw.jspx) that should not be cached. If Oracle Web Cache runs for the application, need to add cache rule to exclude pages with name of /adwwls/wls.ads or adw.jspx.

Mutable Primary Keys in Model Objects (6894412)

ADF Faces components expect applications to use primary keys on the model which are pre-populated for new records and do not change with any record updates. If an application cannot pre-populate primary keys in the data objects for any reasons and the data objects are bound to tables, trees or treeTables, it needs to have the following configuration to workaround potential failures due to primary key value changes:

  • The component inside a column for the primary key attribute should set "autoSubmit=true", and
  • The table, tree or treeTable should set "partialTriggers" property to include the component inside a column for the primary key attribute, and
  • Any selectOneChoice component inside a column should not set "required" property
  • Here is an example:


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

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.

Trinidad application and new Window detection (8677612)

New Window Detection logic only works in Rich Client applications, but not in Trinidad applications For Trinidad applications, the following parameter should be added in web.xml to disable New Window Detection logic.




 <context-param> 
 <param-name>oracle.adf.view.rich.newWindowDetect.OPTIONS</param-name> 
 <param-value>off</param-value> 
 </context-param>

Emailable page Limitations on Tables (8554509, 8868756, 8827678)

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. You need to set the width attribute on the af:column components. (8827678)

Inconsistent Persistence of Customizations when using af:forEach or 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 (e.g. af:forEach) and the repeated component are located in different documents (e.g. in different jsff or jspx files) then will mistakenly allow the customization to persist.

RUEI and UserActivity data

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 when it was originally saved.

Synchronizing Component State When Sharing The Same Iterator Binding

When multiple components share the same iterator binding in a single page, the application needs to use partialTriggers to synchronize UI states. One example is a form and a table based on the same iterator binding. In this case the table's partialTriggers need to point to the form's navigation buttons, in order for the table selection to synchronize with the 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 multibyte characters does not work correctly. Because of this, when you access a page with a multibyte character set name, you may get HTTP Error 404, or a "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 Data Type Support

Due to the lack of support in the model to convert data of type java.util.Date to java.sql.Date, a runtime error will occur if a 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 (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. For example:

@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.

    ADF DVT Graph and Gauge (6904435, 6016950)

    • 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, oracle.adf.view.rich.dvt.DEFAULT_IMAGE_FORMAT, 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. Flash content, including ADF DVT Graphs and Gauges, prints fine when the browser is IE. Applications should use printable page mode to print Flash content or set imageFormat to HTML5 or PNG. (6904435, 6016950)
    • The following are now deprecated:
      • <dvt:numberFormat> tag is now deprecated. Developers should use the standard Trinidad converted tags, e.g. <af:convertNumber>.
      • imageFormat="AUTO" is now deprecated. A new value for the imageFormat attribute imageFormat="HTML5" is now supported to allow for explicit usage. When HTML5 is selected, a fallback (Flash or PNG, depending on the flash-player-usage parameter in adf-config.xml) would be used if the browser doesn't fully support HTML5.
    • If using Internet Explorer 9, the users are advised to use HTML5 or the latest Flash plugin version for that browser

    ADF DVT Pivot Table

    (8895660, 8316539, 8742733, 8998375, 9020333, 9047467, 9012546, 9475191, 11901316, 11890996, 11797618, 10629477, 9931714)

    • 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)
    • Size column of editable pivot table is misfunctioning in Chrome 10. (11901316)
    • Page.findControlBinding method throws a NullPointerException if component is PivotTable. (11890996)
    • 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)

    ADF DVT PivotFilterBar

    (8777349, 9002516, 8777330, 8940695, 8914128, 8917681, 9672617, 9926815)

    • 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

(8914616, 8684652, 9027856, 9026200, 8862734, 9685840, 9083323, 9432601, 9868647, 10635436, 11735740, 11869693, 11901244, 9931735)

    • 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)
    • Accessibility/Jaws issue on table side of gantt: Jaws does not read each individual cell. The workaround is to use INSERT+SHIFT+PAGE UP to read the contents of the entire row. (11869693)
    • 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)

    ADF DVT Databinding and Design Time

    (13683885, 8965391, 8607695, 8926518, 8862266, 8872334, 9708226, 13403532, 13496681)

    • There is a known issue where the oracle.adf.view.rich.dvt.DEFAULT_IMAGE_FORMAT context parameter may be automatically added to the application's web.xml file when opening jspx pages. This context parameter switches the default image format of the graph and gauge component to use HTML5 technologies when supported by the client browser. While the HTML5 output format is recommended, it is possible to opt out at this time by removing the context parameter or by explicitly setting the imageFormat attribute on the jspx pages (13683885).
    • 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)
    • When editing a DVT Graph or Gauge during design time, the enumeration for the ImageFormat property does not list "HTML5" as a valid option. You can set this value in the Source Editor. (13403532)
    • When editing multiple DVT Graphs of the same type within the same page during design time (e.g., two Bar Graphs, two Pie Graphs, etc.), editing the Title of one Graph and then selecting the other Graph to edit its Title could end up changing the Title of the first Graph instance. As a workaround, select another component on the page (or any other Graph child tag) before attempting to edit the Title of the second Graph instance. (13496681)

      • ADF Faces doesn't support surrogate characters in FireFox (bug9063502)

      When you have some surrogate characters to display in ADF Faces page in Firefox2.0 or later, one surrogate character will display as two separate characters. On microsoft IE, there is not this issue.

ADF Share

Resource Bundle Key Not Found for Localized Exception (11779435)

If a JboException is used to throw an exception which is localized, ADF does not search in the correct resource file for the property.

Workaround: Adapt the code in the Class PropertyListResourceBundle as shown, where you test if the value returned by getLocale() is null, and call ResourceBundle.getBundle(getBundleName()) when this is the case.



 
...
protected Object[][] getContents() {
 Locale locale = getLocale();
 if (localeContents.containsKey(locale)) {
 return (Object[][]) localeContents.get(locale);
 }

 ResourceBundle rb = null;
 if (locale == null)
 rb = ResourceBundle.getBundle(getBundleName());
 else
 rb = ResourceBundle.getBundle(getBundleName(), locale);
...

Accessibility Issues

JSP and HTML visual editor toolbar not keyboard accessible (8351632)

When opening the visual editor you may not be able to see all the toolbar functions available and there is no visual indication [... or =>] that more toolbar functions are available. You can, however, expand the window wider to see them all.

Viewing a page preview from the visual editor (8351673)

When viewing a page preview from the visual editor using the default browser users should:

  1. From the main menu, click Tools=>Preferences...=>Shortcut Keys
  2. Locate the JSP and HTML Visual Editor
  3. Preview in Browser and assign a key
  4. Click OK and push button to close preferences.

This option will now be keyboard accessible.

Message dropdown not accessible (8728885)

When working in a facelet and attempting to drop a JSF html message component onto the page, a dialog appears to allow the user to specify the ID to which to attach the message. The workaround is to use the Property Inspector to change the 'for' property of h:message.

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. (6931494)

Keyboard Selection Request Frequency (6238722)

When interacting with an af:table, af:tree, or af:treeTable, using the up or 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 becomes free. Ideally, no request would be sent until after the user has reached the item that they intend to select - that is, until after the user has paused keyboard activity for some short period of time. (6238722)

Read-Only Input Components (5889673)

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 - that is, 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. (5889673)