Jdeveloper 11.1.1.9.0 Download
Product management announced the availability of Oracle JDeveloper and Oracle ADF 11.1.1.7.0. This version is aligned with the rest of the compone nt of Oracle Fusion Middleware 11.1.1.7.0. The version has several bug fixes, but also contains some new features that you can leverage. This page consolidates all download links for Oracle Application Development Framework (Oracle ADF). From this page you can download Oracle ADF related software. Please make sure to choose the right sub-version of software that matches the one of your JDeveloper and WebLogic servers.
- If you are migrating from earlier releases to JDeveloper 11.1.1.4.0 as part of the migration to the current release of JDeveloper and you have.generate files, then you need to force any.generate files to be saved by JDeveloper 11.1.1.4.0 in the new format.
- Notes: Consider the following before you begin using this document: The individual Oracle Fusion Middleware 11 g Release 1 (11.1.1.9.0) products are often announced and released on the Oracle download sites on separate schedules. This document provides an overview of the 11 g Release 1 (11.1.1.9.0) downloads. It is not a comprehensive list.
Oracle JDeveloper 11g Release 1 (11.1.1.9.0) Release Notes - Known Issues
Last Updated May 11, 2105
This document lists known issues for this release. As new issues arise, they will be added to this document. We welcome and encourage your feedback. Your input helps us make the product better. Please use the JDeveloper community discussion forum on OTN for questions and answers, as well as to let us know what you think!
General Issues
Installation
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):
- Open the jdev.conf file. The file is located in the MW_HOME/jdeveloper/jdev/bin/ directory.
- Add the following line to the jdev.conf file: AddVMOption -Djava.io.tmpdir=/var/tmp
Installation on Linux appears to hang while updating file permissions (16810229)
During installation on Linux, the JDeveloper installer updates the default file permissions. This takes a few minutes, and the progress indicator does not move during this time.
Database Development
Error message when you have one or more unsupported database objects in the Database Cart (15903849)
If you try to deploy unsupported objects to an Oracle Database Cloud Service connection you will see an error message. Unsupported objects are, for example, external tables, database links, materialized views, materialized view logs, synonyms, objects from a non-Oracle connection type, objects that use an unsupported datatype. For more information about the database objects that are not supported, see 'Database Cloud Service Features and Implementation Considerations' which is available on Oracle Technetwork at http://docs.oracle.com/cloud/CSDBU/differences.htm.
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 the current release of JDeveloper 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.
Connection to SQL Server Fails with Bundled JDK 6u29 (20002830)
When you create a connection to SQLServer using the bundled JDK 6u29, the connection will fail to connect to the database. The workaround is to download and use JDK 6u30 or later.
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.
From JDK 7 Update 21 onwards, applets will no longer run under default security settings (16432858)
If you are using Java Web Start (JNLP) files, starting with JDK 7 Update 21, applets will no longer run under the default security settings unless the applet is signed by a trusted certificate authority. For more details, refer to the Java web site at http://www.oracle.com/technetwork/java/index.html.
Ojdeploy Behavior Change When Using -nodependencies (16073770)
In earlier versions, the -nodependencies flag prevented deployment from following Project to Project dependencies, now this flag also prevents Profile to Project dependencies. Ojdeploy will only compile and package the targeted project's contents.
This also means that EAR profiles, which use profile dependencies to assemble other Java EE modules, will not deploy those automatically. Each composed module must be individually packaged using ojdeploy before the EAR is deployed.
Deployment Exception When Deploying to WebLogic Server
If you are deploying your application to WebLogic Server but deployment fails with a NoClassDef exception because of a memory leak,
you need to check your application's weblogic-application.xml file and change the ADFApplicationLifecycleListener entry to ADFApplicationStateListener.
After you have made the change, you must apply WebLogic patch 1036 before you deploy the application.
Web Services Development
Some combinations of features can result in JDeveloper running out 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:
- *# 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.
- 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.
- 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);
Minecraft 1.11.0.1
ADF Faces and Data Visualization
- Browser specific bugs** IE9 inputComboboxListOfValues in table or treeTable - The af:inputComboboxListOfValues component will not function properly inside of table or treeTable components.
- IE7, IE8, IE9 layout components - In some layout components, images in the af:commandImageLink component are clipped. Application Developers can fix this by setting the styleClass='AFLinkIEWorkaround' element on the af:commandImageLink tag.
- IE7 nested table elements - If you have nested table elements and an input element with % width, the input field grows when you type into it (Oracle IE7 bug 9869651).
- IE7 inputFile component - The af:inputFile component allows the user to type in the name of a file. This can cause problems if the file does not exist. For reasons like this, IE8 does not allow the end-user to type in the filename.
- IE10 Select Choice component - Due to a bug in IE10, the select choice component does not open up the selection list until focusing on another UI control first then focus on the select choice component (Oracle IE10 bug 16046192).
- IE browser, page appears to hang after closing child window. - After opening and closing new child browser windows several times, the browser has no available connections to service normal requests and appears to hang. The workaround is activated using a skinning property key in a custom skin and applies to all supported browser, .AFWorkaround . This issue is caused by the inability to cleanup inflight requests for what is call the property delta sync. Our components do not just exist on the server. We have a representation that exists on the client. When properties are changed on the client, we queue a property change event. The property change event hitches a ride on the next request to the server. If the page unloads before the delta of property changes on the client have not been persisted to the server, then we try to sync up this state. This is particularity important for component properties that are registered with the change manager. For these properties, their state has a longer life span than the component tree in which they are defined. The property delta sync is an asynchronous request with no guarantee of delivery.
- Firefox 3 Access Keys - Access keys do not work properly on the af:inputFile component (Bugzilla bug 554099), and on the af:selectManyShuttle and af:selectOrderShutle components in screenreader mode (Bugzilla bug 554104). The workaround is to use tab key instead to access the component.
- Firefox 3 Enter key in the Rich Text Editor - Pressing the Enter key in the Rich Text Editor's text field loses the selected font name because of a Firefox queryCommandValue bug (Bugzilla bug 409788).
- Firefox 2 - The cursor is not visible on text fields in popup or table components Bugzilla bug 226933). There are several other rendering issues in Firefox 2 that are fixed in Firefox 3. Mozilla no longer supports Firefox 2, so we are unable to get any fixes for that browser from them. We recommend that if customers run into rendering issues on Firefox 2 that they move to Firefox 3.
- Desktop Safari 3 - The af:richTextEditor component does not function properly in WYSIWYG mode (Webkit bug 7138), many keyboard shortcuts do not work properly.
- Google Chrome - When users press Ctrl-N or Ctrl-T to launch multiple Chrome browser windows and then copy the URL to bring up pages with active data, active data doesn't work correctly (Oracle bug 8309340).
- Calendar, RichTextEditor, and PanelCollection's toolbar icon selectors 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. This is tracked with Bug 11939264.
- NLS Issues with JDK 1.6-only Locales 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. Bug 6859992.
- Profiler File Logger The profiler file logger can be used only in a non-portal environment on FF and IE browsers with at least 1.5._06 JRE on the client box and privilege to write to the user home dir. The resulting file format is subject to change without any notice and not intended to be used with any xml parser tool. In order to use the feature, the user has to accept the certificate.
- StringIndexOutOfBoundsException in org.apache.myfaces.trinidadinternal.style.util.CSSGenerationUtils (9400134) This error happens due to bug http://bugs.sun.com/view_bug.do?bug_id=6875866 (HotSpot compiler bug in String.indexOf() using SSE4.2 instruction-set on new Intel chips). Workaround: Add this line to the JVM options: -XX:-UseSSE42Intrinsics then remove the cached CSS file, (e.g. $APP_TMP_FOLDER/public/adf/styles/cache/blafplus-desktop-ezog8j-en-ltr-gecko) -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
- 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 If Active Data Service is enabled in an application, there are certain ADS pages (/adwwls/wls.ads and adw.jspx) should not be cached. If Oracle Web Cache runs for the application, need to add cache rule to exclude pages with name of /adwwls/wls.ads or adw.jspx. This is tracked via ER 6926281.
- Primary Keys from Model ADF Faces components expect applications to use primary keys on the model data objects that are pre-populated for new records and do not change with any record updates. 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}'
>
<af:inputText value='#{row.bindings.Empno.inputValue}'
.. autoSubmit='true'>
<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}'
>
<af:selectOneChoice value='#{row.bindings.Deptno.inputValue}'
label='#{row.bindings.Deptno.label}'
shortDesc='#{bindings.EmpView1.hints.Deptno.tooltip}'
>
<f:selectItems value='#{row.bindings.Deptno.items}'/>
</af:selectOneChoice>
</af:column>
</af:table>
- Application View Cache The Application View Cache won't work for any page where the rendering of the component tree causes the structure of the component tree to change temporarily. Since this is often the case and the application developer has no way of telling when this will occur, USE_APPLICATION_VIEW_CACHE should never be used. It also only helps initial render performance and does not help the session size. This is tracked via bug 6495920.
- Trinidad app and New Window Detection New Window Detection logic only works in Rich Client applications, but not in Trinidad appliations. For Trinidad applications, the following parameter should be added in web.xml to disable New Window Detection logic. <context-param>
<param-name>oracle.adf.view.rich.newWindowDetect.OPTIONS</param-name>
<param-value>off</param-value>
</context-param>
This is tracked via ER 8677612.
- Emailable Page The table component has some known issues in emailable page mode.
- The Total/Subtotal rows of the table are not bold in Outlook. The application developer would need to define the bold style directly on their outputText. This is tracked via 8554509.
- The detailStamp, if disclosed, does not render as disclosed in emailable page mode in both Thunderbird and Outlook. This is tracked via 8868756.
- columnStretching='last' does not work in emailable mode since this happens in javascript and javascript is not supported by email agents. You need to set the width attribute on the af:column components. This is tracked via 8827678.
- ADF Faces Repeated Components by af:forEach and af:iterator ADF Faces components do not support persisting customization changes if the component is contained inside of (anywhere in the subtree of) af:forEach or af:iterator. However, if the repeating component and the repeated component are located across document, for example, in different jsff or jspx files, then we can't detect this case and will allow the customization persistence.
- User Activity Monitoring and Browser Support** Because of a limitation in the IE userData persistence behavior, the userActivity data for previous requests may be partially or sometimes completely unavailable when accessed from pages with a different URL than was used when the page was originally saved. In IE 5 and later, data stored using IE userData persistence is accessible only to web pages within the same directory and on the same domain. This means that a webpage in a sub folder though part of the same origin cannot access the data persisted by a page in its ancestor folder (8809021). Additionally when IE userData persistence is disabled, client-side tracking of user activity data will be unavailable (it's recommended that the Oracle RUEI feature be explicitly disabled in this case).
- In Safari when a user goes into Private Browsing mode, user activity monitoring will be disabled and as a result no user activity data will be reported. The reason for this is because the DOM sessionStorage object is unavailable for storing any data and attempts to set a value on it throws an error (14368121).
- Accessility: Column Headers for Total/Subtotal Cells ADF Faces users can typically produce accessible table content by specifying column headers for every column in their af:table. However, in certain complex cases, such as when the af:table contains total or subtotal rows, the cell containing the labels for these rows may be inappropriately associated with the containing column's column header. For example, assuming a column contains employee names and has the header text 'Employee Name', a cell containing the text 'Total' will be inappropriately identified to screen reader users as being an 'Employee Name'. In order to avoid confusion, such cells should not be associated with any column header. ADF Faces does not provide any mechanism for suppressing column headers for such cells. Bug 6931494 has been logged to track this issue.
- Accessibility: Keyboard Selection Request Frequency When interacting with an af:table, af:tree, or af:treeTable, using the up/down arrow keys to change the selection can result in a round trip to the server. ADF Faces already optimizes to reduce the number of round-trips by only sending a single request at a time, and also by dropping requests for intermediate selection states that occur while a request is outstanding. However, in some cases keyboard users may find the current behavior inefficient, since a request is sent to the server as soon as the request queue frees up. Ideally, no request would be sent until after the user has reached the item that they intend to select - ie. until after the user has paused keyboard activity for some short period of time. Bug 6238722 has been logged to track this issue.
- Accessibility: Read-Only Input Components Currently read-only input components, such as af:inputText, are rendered by ADF Faces as plain text. As such, there is a loss of information that may be meaningful to screen reader users - ie. screen reader users have no way to determine that the text in question corresponds to a input control. In addition, since plain text content is not included in the tab navigation order, screen reader users may fail to recognize that this read-only content is present on the page. Bug 5889673 has been logged to track this issue.
- UI Components State Sync When Sharing The Same Iterator Binding When there are multiple components share the same iterator binding in one page, the application needs to use partialTriggers to sync up UI states. One example is a form and a table based on the same iterator binding, the table's partialTriggers needs to point to the form's navigation buttons, for table selection to sync with form.
- Multibyte Character Set Page Name: not supported for WebSphere Application Server Due to WAS's specific implementation of HttpServletResponse class, server side redirect for UTF-8 encoded URL with MBCS characters does not work correctly. Because of this, when you access a page with multibyte character set name, you may get Http Error 404, or 'Failed to find resource' error.
- Resource URL Session ID Rewriting In some scenarios a session id may be inserted into URLs for ADF Faces resources such as JavaScript libraries, style sheets and images. This can happen when cookies are disabled in the user's browser or the first time that a user visits an ADF Faces application, at which point the application server does not yet know whether cookies are enabled. While this does not impact functionality, it can result in a small performance hit, since the presence of the session id prevents previously cached copies of resources from being used. In cases where the application requires the use of cookies, it is possible to avoid session id URL rewriting by configuring the application server to always use cookies for session id management. For example, Oracle WebLogic Server allows session id url rewriting to be controlled by the <url-rewriting-enabled> element in the weblogic.xml file.
- Calendar Binding data type support
Due to the lack of support in model to convert data of type java.util.Date to java.sql.Date, a runtime error will occur if java.sql.Date is specified as NDType in the calendar page definition file. Please use the supported types instead:- oracle.jbo.domain.Timestamp
- oracle.jbo.domain.Date
- java.sql.Timestamp
- java.util.Date
- Dialog Framework, new browser window, and RTL Locale - Bug 12630300 identified a layout issue with IE version 9 and greater, Microsoft SR 111072584108293. This issue is further isolated to the use of the dialog framework launching a new browser window and only when the locale is RTL. This SR is targeted for IE10 but it is unknown yet if it will make this release. As a workaround the .AFDialog-tr-enable-ie-rtl-toggle skinning property key can be used to enable a workaround. This workaround is not implicitly activated. It must be enabled in a custom skin. Consider: @agent ie and (version:9) Unknown macro: { .AFDialog{ -tr-enable-ie-rtl-toggle}}
- Using HTML 5 features in Internet Explorer 9 Unlike most browsers supporting HTML 5 features, Internet Explorer 9 requires the presence of the HTML 5 DOCTYPE to enable these features. Unfortunately, ADF Faces currently generates Internet Explorer content in almost standards mode. Changing to the HTML 5 DOCTYPE without changing the way some of the DOM is generated would result in layout changes. We are working on addressing this issue.
- convertDateTime may not work with pattern 'MMM' on Websphere Application Server (WAS)
On IBM JDK deployments (WAS), date patterns which contain 3 or more letters for the month, e.g. 'MMM' may fail, e.g. on locale 'zh_HK' it fails with a Javascript parse error even though the user has not modified the value. This is tracked as bug 14088506. - Client NumberConverter does not work with tr_TR locale and type=percent
In Turkish (tr_TR) locale, numberConverters with type=percent do not allow users to enter a number, but will throw a Javascript error even if the input is valid. This is tracked as bug 13006484. - Client DateTimeConverter does not work with dateStyle=full and locales th_TH or ja_JP_JP
When the dateTimeConverter is used with dateStyle=full or locale=th_TH or ja_JP_JP, there will be a Javascript error thrown even though the date is valid. This is tracked as bug 12861287 - No Oracle-hosted resources for emailable attachments (16546053) Oracle has decided to not publicly host ADF resource files on Oracle-owned servers for the purpose of supporting ADF faces content in email attachments. This information will be removed from the documentation in a subsequent update.
- InputFile component in multiple file upload mode using IE When an InputFile component configured to support multiple file upload is used with IE with Java enabled, the following settings must be set.
- In the IE security level for the zone, the option 'Include local directory path when uploading files to the server' must be enabled.
- If the InputFile component is in a popup then in the Java Control Panel under Advanced->Java Plug-in, the option 'Enable the Next Generation Java-Plugin' must be disabled.
ADF Data Visualization Components
ADF Data Visualizations General
New Chart and Gauge charting solution is now available. The new charting components are purely client-side, offering superior performance and user experience. They are used by both Mobile Application Framework and ADF.
As part of the design time in 11.1.1.9 the old Graph and Gauge tags have been deprecated in cases where the new tags offer an equivalent Chart or Gauge type. As a result, we will not expose Data-First nor UI-First creation of the deprecated tags -- instead, the design time will generate the new tags. Editing existing border='1' cellpadding='1' cellspacing='1'>Old Tag (Deprecated)New Tagdvt:areaGraphdvt:areaChartdvt:barGraphdvt:barChartdvt:bubbleGraphdvt:bubbleChartdvt:comboGraphdvt:comboChartdvt:funnelGraphdvt:funnelChartdvt:gauge
dvt:horizontalBarGraphdvt:horizontalBarChartdvt:lineGraphdvt:lineChartdvt:pieGraphdvt:pieChartdvt:scatterGraphdvt:scatterChartADF Data Visualization Graph and Gauge
- Flash rendering for DVT Graph and Gauge is no longer supported. DVT Graph and Gauge components are now rendered in HTML5 instead of Flash, and there is no functional difference between the output formats.
ADF DVT Pivot Table
- In order to store edits, the PivotTable needs to be bound to a DataControl/Model that supports writeback operations. A Rowset based DataControl, like the BC4J based DataControl, is transformed into a cube and, due to the transformation, cannot support writebacks. (8895660)
- When using Internet Explorer in BIDI mode the PivotTable scrollbars can sometimes reset to their original position. (8316539)
- After editing a cell then sorting, column sorts on original value, not new value. (8742733)
- Sorting in PivotTable blows away existing sorts. (8998375)
- Pivot with keyboard can interfere with some graphics cards. (9020333)
- User resizes are sometimes forgotten. (9047467)
- Ability to make selections lost after pivot to PivotFilterBar. (9012546)
- Pivot Table does not have touch gesture support for row/column resizing on iOS. (9931714)
ADF DVT Pivot Filter Bar
- 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)
- Keyboard pivoting from PivotTable to PivotFilterBar component not working, vice versa works. The workaround is to use drag and drop operation. (8917681)
- Export of PivotTable data to Excel when stamping is used ends up with duplicated values in the cells. (9672617)
- Leading zeros are not carried from the pivot table to exported Excel. (9927815)
ADF DVT Gantt Chart
- Label alignment does not shift when impossible to show label as defined. For example, a task with left-aligned label is placed all the way to the left. (8914616)
- Issue when zoom using scroll wheel using Safari browser, CTRL-Scroll wheel is reserved for Browser font resizing. (8684652)
- Rollover text can appear beneath the chart right-mouse menu. (9027856)
- Tag documentation for the project gantt and initialDateFocus is incorrect. (9026200)
- Some debug messages appear in console when creating a Project Gantt. (8862734)
- Regions in popup window are not getting painted properly when launched from Gantt. (9685840)
- NullPointerException is sometimes thrown when collapsing rows in Project Gantt. (9083323)
- SchedulingGantt: NullPointerException sometimes gets thrown on data change event (9432601)
- Time value in tooltip of DataChangeListener is incorrectly calculated. (9868647)
- Scheduling Gantt DT design-time view in JDeveloper gets converted into the tag-boxes view when a startTime and/or endTime are set from a backing bean. (10635436)
- Scheduling Gantt: 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 Timeline
- Timeline could become unresponsive if the initial start and end time fits into the page without scrolling and user then zooms to a scale that causes the timeline to be extremely wide. Workaround is to specify an end time such that the timeline is wider than the viewport. (16080267)
- TimelineOverview is not re-sized when placed inside a stretchable container and the user increased the horizontal size of the container. (14532594)
- In the vertical Timeline, markers sometimes dissapear in the overview window after maximizing the browser window. (19913080)
ADF DVT Databinding and Design Time
- 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:
- Edit the corresponding PageDef source;
- Find the corresponding element in thesection of the Pivot Table binding;
- Update the 'label' attribute of that element to the correct alternate attribute name. (8607695)
- Live data preview in DVT binding dialogs is no longer available. To preview how a data visualization component will look with live data, you can run the page with the integrated WLS. (17960253)
ADF Business Components
ADF Business Components Runtime Parameter jbo.ampool.writecookietoclient Must Not be Modified (16846118)
The runtime ADF Business Components application module pooling parameter jbo.ampool.writecookietoclient is no longer required by ADF Business Components. Do not change the default value (false). The default is not to create a browser cookie. This parameter was formerly used to write the SessionCookie value to the client browser. This parameter also appears in the Enterprise Manager Fusion Middleware Control as AmpoolWritecookietoclient where its default value must not be changed.
Deprecated Usage of Method notifyUpdatedRow(ViewRowSetImpl, Row[], int[]) (15987168)
When overriding methods in the ViewImpl class of an ADF Business Components project, you must not override the 'notify row updated' method with this signature:
(deprecated) protected void notifyRowUpdated(ViewRowSetImpl vrs, Row[] viewRows, int[] attrIndices)
In JDeveloper the audit rule 'notifyRowUpdated Method Parameters' will update all occurrences of this deprecated method to use the method with this signature instead:
(valid) protected void notifyRowUpdated(ViewRowSetImpl vrs, Row[]viewRows, int[] attrIndices, UpdateEvent updateEvent)
Note that it is important to check for code that calls the deprecated method and to change to the valid method (shown above). Specifically, make sure that the updateEvent parameter is added to the calling method.
Using the method with the updateEvent parameter ensures that the RowInconsistentException is thrown when two users attempt to change a row referenced by the same primary key from independent application module sessions.
Synchronize with Database action duplicates entity associations (9036179)
When you create entity objects and associations based on database tables and subsequently make changes to the database (such as adding a column to a table), you can use the Synchronize with Database action in JDeveloper to propagate those changes to the generated entity objects. However, if the associations are not stored in the same package as the entity objects, the Synchronize with Database action will create duplicates of existing associations.
For example, say you have set the preference for the package name for associations to entities.associations in the Preferences dialog (Tools > Preferences). Then when you use the Business Components from Tables wizard (available from the New Gallery) to generate business objects, including entity objects and associations, the associations are created in a subpackage of entities called associations. After adding a column to the EMP table, for example, you use Synchronize with Database to update the Employee entity object. This action generates a duplicate association with a slightly different name:EmpDeptFkAssoc -- the originalEmpDeptFk1Assoc -- the new duplicate
When this happens, you can simply delete the new duplicate associations. To avoid this situation, you can set the preference for the package name for associations to use the default, which is the same package as the entity objects.
Multiple SQL Flavors Not Supported Across ADF Applications Running on the Same Managed Server (25903995)
Support for using multiple SQL flavors across ADF applications running on same server is not implemented nor supported by ADF. ADF application developers must therefore ensure that ADF applications that they plan to run in the same managed server all use a single value for their SQL flavor. At design time, the SQL flavor can be set either at the project level using the Initialize Business Components dialog or globally in the adf-config.xml file. Regardless of the approach used to set the SQLBuilder property, in practice, the value must be the same for all ADF applications running on the same managed server. Failure to implement this requirement can result in runtime conflicts in the binding style that ADF will use to process query statements and this in turn will cause SQL validation errors for the applications. Additionally, it is important to note in the scenario where an ADF application needs to run against both Oracle and non-Oracle databases, all applications on the same managed server must have SQL92 chosen as their SQL flavor.
ADF Model
Deprecated Usage of invokeAction in the Binding Editor Dialog (16245889)
Windows 10 pro activate crack. The invokeAction executable has been deprecated in Oracle ADF 11g release 11.1.1.7.1. Oracle recommends that developer use a method activity in a task flow to call an action binding (or any backing bean method) to perform some application behavior before the page is rendered. For example, for a page used to create an object, you might have a task flow that begins with a method activity that calls the CreateInsert operation. The task flow then proceeds to the view activity for the page where the user inputs data. Modeling this behavior as discrete method call activities provides a much cleaner separation of application logic and data bindings, making applications both self-documenting and easier to maintain.
ADF Desktop Integration
Versions of Microsoft .NET Framework
- Microsoft has announced that it will end support for .NET 4 (on Windows 7 and Windows 8) starting in January 2016. Microsoft recommends upgrading to version 4.5.2.
- Reference: http://support2.microsoft.com/gp/framework_faq
- ADF Desktop Integration is compatible with .NET 4.5.2. Users may install it at any time. Future versions of ADF Desktop Integration may check for and install this version of the Microsoft .NET Framework.
Web Page Dialogs using af:query components
- Users that go into an af:query component's Advanced query mode in a web page dialog (including the Model-driven List Picker) may experience flickering and unresponsive choice list components. Workaround: include giving focus to a component outside the af:query (eg. the Results Table). Users with Microsoft Internet Explorer version 11 do not experience this issue. (bug 20026213)
Excel Configuration
- The Excel setting known as 'Trust access to the VBA project object model' is only required for integrated workbooks that include ADF Button components. The documentation suggests that this setting is always required. However, it is not required for integrated workbooks that do not contain buttons.
Avoid Select-All in protected worksheets
- If the current worksheet has 'Protect Sheet' mode turned on and the end user performs a 'Select All' operation, Excel can freeze indefinitely. (bug 19504666)
Last updated on JULY 28, 2019
Applies to:
Oracle JDeveloper - Version 11.1.1.6.0 to 11.1.1.9.0 [Release Oracle11g]Information in this document applies to any platform.
Many users preferred method to install the ADF runtime libraries on WebLogic Server was to use the same JDeveloper installer they used to install JDeveloper IDE. Also many users install JDeveloper in the same Middleware home as the other Fusion Middleware products, like WebLogic Server, SOA, and so on.
(NOTE: As a general recommendation, you should install JDeveloper into it's own directory and not on top of an existing Middleware home as WebLogic Server and/or other products.)
The base rule was to follow the Certification Matrix for Application Servers and match versions with WebLogic Server:
- JDeveloper/ADF Runtime 11.1.1.1.0 with WebLogic Server 10.3.1
- JDeveloper/ADF Runtime 11.1.1.2.0 with WebLogic Server 10.3.2
- JDeveloper/ADF Runtime 11.1.1.3.0 with WebLogic Server 10.3.3
- JDeveloper/ADF Runtime 11.1.1.4.0 with WebLogic Server 10.3.4
- JDeveloper/ADF Runtime 11.1.1.5.0 with WebLogic Server 10.3.5
So far, this was possible through all the 11g installers for JDeveloper, until 11.1.1.6 release. With the 11.1.1.6 and 11.1.1.7 releases, ADF can run on two different versions of WebLogic Server: 10.3.5 and 10.3.6. This presents us a constraint with the JDeveloper installer.
With the JDeveloper 11.1.1.6, 11.1.1.7 installer you can't:
- Install ADF 11.1.1.6, 11.1.1.7 runtime on top of WebLogic Server 10.3.6.
- Install JDeveloper 11.1.1.6, 11.1.1.7 in the same Middleware home as WebLogic Server 10.3.6.
If you try to do it, you will receive an error message. See below.
JDeveloper/ADF Runtime 11.1.1.9.0 is only certified with WebLogic Server 10.3.6
Symptoms
When trying to install JDeveloper/ADF 11.1.1.6, 11.1.1.7 on top of WebLogic Server 10.3.6 you get the error message:
The product maintenance level of the current installer (WebLogic Server:10.3.5.0) is not compatible with the maintenance level of the product installed on your system(WebLogic Server:10.3.6.0). Please obtain a compatible installer or perform maintenance on your current system to achieve the desired level.
Note that JDeveloper 11.1.1.9.0 is bundled with WebLogic Server 10.3.6, so you should not see this error. JDeveloper 11.1.1.9.0 is not certified to work with WebLogic Server 10.3.5.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
Don't have a My Oracle Support account? Click to get started! |
| Symptoms |
| Changes |
Jdeveloper 11.1.1.9.0 Downloads
| Cause |
| Solution |