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

Known Issues for JDeveloper and ADF 11g 11.1.1.5.0

last updated: 27-JULY-2011

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!

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

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

Connecting to Oracle Database Using OCI8 (11718506)

The recommended way of connecting to Oracle Database is using the thin driver, however you can connect using OCI8 by following these steps:

  1. Install the Oracle Client.
  2. Add the Oracle Client to the System Environment Variable PATH.
  3. Edit jdev.conf to include "AddJavaLibFile /path-to-client/ojdbc6.jar".

Warning Messages When Migrating from JDeveloper 10.1.3 (11668213)

When you migrate an application that contains offline database objects from JDeveloper 10.1.3 you will see one or more warnings in the messages log:

oracle.jdevimpl.offlinedb.browser.DBObjectFileWrapper getProvider

WARNING: Offline Database file does not exist for file filename [offlineObjectType]

These appear because of the different way that offline databases are handled in this version, and can be safely ignored. 

Deployment

Problems running WLS on Windows 7 64-bit or Mac (9466912, 8969281)

JDeveloper does not look at the value of CLASSPATH or JAVA_HOME to determine its classpath or jdk; it stores this information in proprietory locations. The WebLogic domain installation scripts, however, extend the supplied value of the CLASSPATH and JAVAHOME variables, and WebLogic domain creation will fail if JAVAHOME contains ')' or CLASSPATH contains a space. The former happens when, for example, the 32bit JDK is installed in its default path, for example: C:\Program Files (x86)\Java\jdk1.6.0_18. The latter if an application such as Apple QuickTime adds itself to the to the CLASSPATH environment variable, for example:

CLASSPATH=.;C:\Program Files (x86)\QuickTime\QTSystem\QTJava.zip

In either of these cases, creation of the Integrated WebLogic Server domain fails with a message similar to: 


 
[waiting for the server to complete its initialization...]

\Java\jre6\lib\ext\QTJava.zip was unexpected at this time.

Process exited.

The workaround is to install the JDK in a path withpout ')', and remove the Apple QuickTime entry from the classpath, and restart JDeveloper.

Web Services Development

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

Unknown macro: { public String[] list(); public String[] echo(String[] value); public void process(int[] values); }

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);

Spring and Weblogic SCA Development

JDeveloper hangs when using Spring tooling without an active network connection (10050723)

When editing a spring bean definition you might experience hangs as the code incorrectly tries to download files from the internet. (In particular datatype.dtd) You need an active network connection to make use of the Spring tools. There is a patch with a fix for the original issue in 10074487 and is fixed by bugs #12712872 and #1235505.

Team Productivity Center Issues

Compatible version of connectors not retrieved

Team Productivity Center installer does not retrieve the compatible version of connectors hosted on Oracle Technology Network.

Workaround:

Open tpcinstaller.jar with winzip or 7-zip

Expand folder META-INF and locate file installer.xml

Edit this file by changing this line

<entry key="VersionPrefix">11.1.1.4.37</entry>

to

<entry key="VersionPrefix">11.1.1.5.37</entry>

Save the installer.xml file and the tpcinstaller.jar file

Team Productivity Center server cannot be started with Tomcat

Team Productivity Center server cannot be started if it is installed using Tomcat.

Workaround:

Make sure you have applied the above mentioned wrkaround

Make sure you have installed JDeveloper Studio version

Run the installer against your Tomcat server

After installation completes, start the Tomcat server and then stop it

Go to your newly installed JDeveloper folder and locate folder "modules". For example, C:\JDeveloper11.1.1.5\modules

Copy the file named "org.eclipse.persistence_1.1.0.0_2-1.jar"

Go to your Tomcat server webapps directory and identify the lib folder used by otpc. For example, C:\Program Files\apache-tomcat-7.0.12\webapps\otpc\WEB-INF\lib

Paste the file "org.eclipse.persistence_1.1.0.0_2-1.jar"

Restart Tomcat

ADF Desktop Integration (ADFdi)

Excel Validation and ADF Table Components (7509432)

Excel validation does not get applied to the placeholder row in an ADF Table component that contains data.

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 is to 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 is to resolve the situation, 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.

Conditional Formatting in Integrated Excel Workbooks (6869548)

Oracle ADF Desktop Integration does not support the conditional formatting features provided in Excel by clicking Home > Conditional Formatting.

Workaround is to use Excel named styles in combination with ADFdi expressions in the component's style properties.

Failure Details for Foreign Key Violations Not Displayed Properly (8262587)

Users may encounter unexpected reports of errors under certain circumstances during the Upload operation for an ADF Table component. The Upload operation processes rows in batches. After posting changes from a batch, ADFdi executes the action specified by the CommitBatchActionID. Errors that occur during the commit action may continue to be reported on subsequent batch commit actions, even though those batches of records do not contain the error. (bug 8262587)

Cause: any pending model changes that exist when the CommitBatchActionID gets called are not automatically reverted when commit fails.

Workaround is to create a custom action for the CommitBatchActionID that first attempts to commit the pending model changes. However, if an exception occurs during commit, the custom method should first rollback the pending model changes, so that any subsequent batch commit attempts can succeed. Note: it is important that the commit exception gets re-thrown after rollback so that the commit error(s) will get reported as expected on the client.

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 instead create variables using the <variable> element in the page definition.

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

  • HTML 'select' components in web pages do not respect z-order as expected when the page is displayed from Dialog actions (bug 7205486)

    Given a web page with layered and overlapping components that is displayed in the .NET Web Browser control used in the Dialog action, it has been shown that HTML 'select' components may appear unexpectedly "on top" of other components. The controls are not respecting the "z-order" configuration as expected. Reference: http://docs.microsoft.com/en-us/collaborate/connect-redirect?FeedbackID=377657

    Workaround is to avoid this problem, use web page control types that are not affected by the problem.

  • 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)

    Workaround is to enhance the web page's bean code to detect a change in the current row and cancel the dialog.

  • 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)

  • Changing list binding metadata can cause unexpected exceptions in workbooks run prior to the change (8575731)

    Scenario: When the application is developed, workbooks published, app deployed, and the published workbooks have already been run by business users. Then, the application configuration is changed.

    Problem: the runtime ADFdi workbooks cache the binding container metadata from the application.

    If the application metadata is then changed, unexpected errors can occur.

    Workaround is to fetch a new copy of the published workbook from the web app, or execute the ClearAllData command

  • 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 involving master-detail worksheets (8770675)

  • Editing value defined in ViewLink between master and detail fails with exception (bug 8770675)

    Symptoms: The business user may see an error like "ADFDI-00117: An unexpected error occurred reading the DIRemoteServlet response." connected to a server error like

    "oracle.jbo.AttrValException: JBO-27014: Attribute XXX in AppModule.YYY is required."

    Editing the ViewLink attribute is not supported since it alters the selections in the child view object.

    Workaround is to define the ViewLink attributes to be read-only. Or, use a Model configuration that does not include a ViewLink between master and detail.

Known issues involving the Read-only Table Component (7626970, 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.

  • Inserting Excel Rows into an ADF Read-only Table Component (bug 7626970)

    Inserting an Excel row into an ADF Read-only Table results in a new Excel row that behaves as if it were part of the downloaded data set. In fact, the new row exists only in Excel.

  • 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 issue with Excel's 'Page Layout' mode (7482216)

  • Summary: if the workbook developer switches the View mode of Excel to "Page Layout", ADF Button components may be rendered in an unexpected position (bug 7482216).

    Workaround: Switch Excel back to Normal View mode. Then, Run and Stop the workbook so that the buttons will redraw correctly.

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.5.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()". See 'Updating Fusion Middleware Shared Libraries' in the 'Oracle Fusion Middleware Patching Guide' available on the Oracle Fusion Middleware Documentation Library link: http://docs.oracle.com/cd/E17904_01/index.htm Use the following path: Install, patch, and upgrade > Applying the Latest Oracle Fusion Middleware Patch Set > Post-Patching Tasks > Updating Fusion Middleware Shared Libraries.
  • Cannot upload saved changes from 11.1.1.3.0 workbook after migration to 11.1.1.5.0 (bug 10358830)

    Solution: Prior to upgrading to 11.1.1.5.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.5.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.5.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 to access the old version. These errors can be dismissed and ignored.

    Assuming that you are migrating 11.1.1.3.0 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.

ADFdi ribbon tab not displayed (add-in inactivated or disabled by Excel) (9778270)

Under certain circumstances, the ADFdi add-in for Excel may become inactivated or disabled (bug 9778270).

One symptom of this problem is that the ADFdi-related Excel ribbon tabs may not appear when expected.

Workarounds:

  • In Excel, open Excel Options and select Add-Ins. Look for the ADFdi add-in ('Oracle ADF 11g Desktop Integration Add-in...') in the list. If you find it in the Inactive Add-ins section, attempt to re-activate it by selecting 'COM Add-ins' from the Manage menu and clicking the Go button. Ensure that the checkbox is checked in the 'Add-ins Available' list.

    If the ADFdi add-in appears in the Disabled Add-ins section, attempt to re-enable it by by selecting 'Disabled Items' from the Manage menu and clicking the Go button. Select the ADFdi add-in in the Disabled Items dialog and click the Enable button. Close Excel and then re-launch it to allow the ADFdi add-in to re-initialize and display the expected ribbon tabs.

    Reference: http://msdn.microsoft.com/en-us/library/ms268871%28v=VS.90%29.aspx

  • Or, uninstall the ADFdi client software from the Windows Add/Remove Programs control panel, and then re-install it. (Note: for a disabled add-in, re-installing may not be sufficient, see instructions above for re-enabling the add-in).

Known issue with date-time values and time zone changes (10623397)

Consider the following sequence of events (bug 10623397):

  • The end user downloads data with the local laptop computer configured for one time zone (e.g. PDT)
  • The user saves and closes the workbook
  • The user travels to another timezone and adjusts the computer time zone to the local time zone (e.g. EDT)
  • The user edits some data and performs an upload

Result: Any date-time values from modified rows will be considered to have changed by the difference in the time zones.

Analysis: Date-time values in Excel do not have any notion of time zone. ADFdi always uses the local computer's time zone to adjust date-time values before communicating with the server.

Workaround is to complete the upload of any pending changes before altering the local computer's time zone settings.

After altering the local computer's time zone settings, be sure to re-download worksheet data before making any modifications.

ADF Faces and Data Visualization

Browser Specific Bugs

See browser specific bugs listed in the Supported Platforms section (http://adfui.us.oracle.com/releases/adf.faces/11.1.1.5.0/release.html#SupportedPlatforms)

Calendar, RichTextEditor, and PanelCollection's toolbar icon selectors (11939264)

When skinning icons and images, a '/' at the beginning of the url means context-relative, and a '//' means server-relative. http://myfaces.apache.org/trinidad/devguide/skinning.html#urls However, for the calendar toolbar icons (e.g., af|calendar::toolbar-day-icon), a '/' does not work, and a '//' means context-relative. For richTextEditor and panelCollection's toolbar icons (e.g., af|richTextEditor::bold-icon, af|panelCollection::freeze-icon), both '/' and '//' mean context-relative. T

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

    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.

    Primary keys from model (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 (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 (8827678)

      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.

    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.

    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.

    ADF Faces Table Column Reordering

    In af:table, when you have a detail stamp and you keep the detail stamp expanded, then table column reordering won't work.

    To work around this, you can collapse the detail stamp first and then do the column reordering.

    Accessibility: Column headers for Total/Subtotal cells (6931494)

    ADF Faces users can typically produce accessible table content by specifying column headers for every column in their AF:table. However, in certain complex cases, such as when the AF:table contains total or subtotal rows, the cell containing the labels for these rows may be inappropriately associated with the containing column's column header. For example, assuming a column contains employee names and has the header text "Employee Name", a cell containing the text "Total" will be inappropriately identified to screen reader users as being an "Employee Name". In order to avoid confusion, such cells should not be associated with any column header. ADF Faces does not provide any mechanism for suppressing column headers for such cells.

    Accessibility: Keyboard selection request frequency (6238722)

    When interacting with an AF:table, AF:tree, or AF:treeTable, using the up/down arrow keys to change the selection can result in a round trip to the server. ADF Faces already optimizes to reduce the number of round-trips by only sending a single request at a time, and also by dropping requests for intermediate selection states that occur while a request is outstanding. However, in some cases keyboard users may find the current behavior inefficient, since a request is sent to the server as soon as the request queue frees up. Ideally, no request would be sent until after the user has reached the item that they intend to select - ie. until after the user has paused keyboard activity for some short period of time.

    Accessibility: 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 - 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.

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

This error happens due to bug 6875866 (HotSpot compiler bug in String.indexOf() using SSE4.2 instruction-set on new Intel chips).

Workaround is to add this line to the JVM options: -XX:-UseSSE42Intrinsics, then remove the cached CSS file, e.g., $APP_TMP_FOLDER/public/adf/styles/cache/blafplus-desktop-ezog8j-en-ltr-gecko-1.9.1.8-cmp.css restart WLS, clear your browser cache and everything should be working.

Please note that the bug should be fixed with jdk6.18b02 but we see it on 6.18b07

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.

Popup components with the childCreation attribute set to "deferred" often render blank with the first invocation

This issue arises if you use the popup component with a region and use the setPropertyListener tag to establish the activation of the region. The setPropertyListener tag with a popupFetch type will not be invoked for the initial fetch establishing the initial content delivery. This is because the markup that defines the setPropertyListener tag is defined within the popup's body. With the option to defer creating the children, the body is not processed until the first fetch for content. The popup fetch event listener (setPropertyListener) is processed in the Apply Request Values phase prior to when it is created in the Render Response phase. The workaround is to use the "popupFetchListener" method expression (PopupFetchEvent server-side event) to establish state that would have been established using the setPropertyListener.

UIXCollection stamp state carry-over

Due to a bug, it is possible for some of the component state to appear in the wrong rows for the collection family of components (iterator, table, treeTable and tree). The problem manifests itself in different use cases.

  1. Disclosure state carried over from last row to a new row. Given a disclosure component, like <af:showDetail/>, adding a new row to a collection component, the new row's disclosure component may pick up the disclosure state of the last row of the collection.
  2. Submitted values may carry over from the last row to a new row. If the event that submits data to the server is either immediate, or bypasses the validation and update model phase of the input components in the collection, the submitted values in the last row may carry over to a new row's input components.

    Besides an immediate event, an example of when validation and update model may not occur is if <af:subform/> is around the input components.

  3. Nested collection components may share the stamp state across parent rows when rows are added. For nested collection components (iterator in an iterator, table in an iterator, etc.), when new rows are added to the page, the new rows in the nested component may share the component state with other rows in the parent iterator. For example: 
    
 
<af:iterator id="outer" var="outer" value="#{...}">
  <af:iterator id="inner" var="inner" value="#{...}">
    <af:inputText id="text" label="Input text" value="#{...}"/>
  </af:iterator>
</af:iterator>

    In this case, the text component may end up sharing the stamp state of other iterations. So, if there are two items in the outer iterator and 2 items in the inner iterator, outer row 1 with inner row 1 may end up sharing its stamp state (submitted value) with the outer row 2 and inner row 1 instance.

To work-around this issue:

  • Avoid using immediate="true" or af:subform to stop validation and update model for rows in a collection component.
  • Use click-to-edit on tables instead of edit-all.
  • Minimize, where possible, when nested iterators or tables are in use.

JSF 1.2 Migration

With ADF Faces now requiring JSF 1.2, it is recommended to migrate your project and its containing files to JSF 1.2 when prompted in JDeveloper. If you choose not to migrate, ADF Faces DT will still provide support for the following changes:

  • af:attribute -> f:attribute - This will be flagged as an error. The DT will present the fix to do the conversion.
  • af:validator -> f:validator - This will be flagged as an error. The DT will present the fix to do the conversion.
  • ID's in af:forEach or c:forEach children - This will be flagged as an error for the components inside of the forEach tags. The DT will present the fix to remove the ID's of the contained components.
  • af:forEach -> c:forEach - This will be flagged as a warning, as it's a performance improvement and negates the use of the varSttaus variable. This will only be flagged if we find an af:forEach where varStatus is not used. The DT will present a fix to do the conversion, including explicit registration of the JSTL 1.2 tag library if necessary.

Note that choosing to migrate when prompted will automatically take care of this for you.

    ADF DVT Graph and Gauge (6904435, 6016950, 8275790, 8977003)

    • 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 PNG. (6904435, 6016950)
    • There are known issues using Flash graphs in BiDi locales. The workaround is to use PNG graph image format. In PNG, static rendering is fully supported, but certain interactive features, such as seriesRolloverBehavior and animation, are not available. (8275790)
    • Graph can not load alert images in a portlet environment (8977003)
    • If using Internet Explorer 9, the users are advised to use the latest Flash plugin version for that browser.
    • 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. Developers should use the new flash-player-usage context parameter in adf-config.xml.

    ADF DVT Geographic Map

    • In Internet Explorer 9, the hand symbol used for selection appears in black color. (11851421)

ADF DVT Gantt Chart (8914616, 8684652, 9027856, 9026200, 8862734, 9685840, 9083323, 9432601, 9868647, 10374397)

  • Label alignment does not shift when impossible to show label as defined. I.e. task with left-aligned label placed all the way to the left(8914616)
  • Issue when zoom using scroll wheel using Safari browser, CTRL-Scroll wheel is reserved for Browser font resizing (8684652)
  • Rollover text can appear beneath the chart right-mouse menu (9027856)
  • Incorrect tag documentation for the project gantt and initialdatefocus (9026200)
  • Some debug messages appear in console when creating a project gantt (8862734)
  • Regions in popup window not getting painted properly when launched from Gantt (9685840)
  • Null pointer exception collapsing rows in project gantt (9083323)
  • SchedulingGantt: NullPointerException sometimes gets thrown on data change event (9432601)
  • Time value in tooltip of DataChangeListener incorrectly calculated (9868647)
  • On-demand fetching/rendering renders entire chart. When using a non-hierarchical rowset and displaying dependency lines, the performance of the Gantt chart is slow as all the rows are being rendered on the client. The workaround is to either use a non-expanded hierarchical rowset and/or disable the display of dependency lines. (10374397)
  • Project gantt: NullPointerException in isContainer() method of Gantt model (12316952)
  • Need ability to maintain the selection order of the tasks selected on the gantt (11676815)
  • SchedulingGantt DT design view -> tag-view when start/endtime comes from bean (10635436)
  • Scheduling gantt region has "no row header found" (11735740)
  • Accessibility/jaws issue on table side of gantt (11869693)
  • Scheduling Gantt: snap to operation leaves a couple of pixels between tasks (11901244)

ADF DVT Pivot Table (8895660, 8316539, 8742733, 8998375, 9020333, 9047467, 9012546, 9475191)

  • 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)
  • Pivottable: size column of editable pivot table misfunctioning in Chrome 10 (11901316)
  • Page.findcontrolbinding throws a NullPointerException if component is pivottable (11890996)
  • ClassCasteEception when reading messages from headerCell (11871123)
  • Unable to use pivottable sizingmanager attribute (11797618)
  • NullPointerException: create printable page with Pivot Table (10629477)

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)
  • Accessibility: 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. Use backing bean instead to set the properties (8914128)
  • Keyboard pivoting from pivottable to pivotFilterbar component not working, vice versa works. Please 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 Databinding and Design Time (8965391, 8607695, 8926518, 8862266, 8872334, 9708226, 11810002, 11716107)

  • 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)
  • If a DVT Geographic Map has either a 'popup' or a 'rtPopup' facet, and if the developer attempts to insert content into either facet from the Structure Pane, the resulting context menu does not display a filtered list of valid facet contents. As a workaround, the developer can add a child tag to the facet in the Source Editor. (11810002, 11716107)

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);
...

Translation and Globalization Issues

'Configurations...' and 'Go to Domain Class' don't work in AppModule right click menu (12319507)

In Japanese locale, AppModule right click menu items 'Configurations...' and 'Go to Domain Class' don't work.

As a workaround for 'Configurations...' menu item, double click AppModule and select Configurations tab in AppModule Overview editor. A simple workaround for "Go to Domain Class" menu item: Expand the Domain node to show the java class, then double click to open the java class directly.

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.