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

Known Issues for JDeveloper and ADF 11g Release 2 (

last updated: June 23, 2011



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 ( for additional details on installing JDeveloper for Mac OS X.

1. Make Java 6 the default VM.

2. Create a symbolic link for classes.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



When you click "Access documentation online" on the QuickStart window (accessible from the Start Menu), you are taken to the Oracle Fusion Middleware 11g Release 1 ( documentation library. The link should take you to the Oracle Fusion Middleware 11g Release 1 ( documentation library, which is available at:


JSF 2.0 Migration

When opening a workspace that uses JSF technology, we migrate the application to JSF 2 by doing the following:

JSF Upgraded to 2.0

The JSF version packaged in has been upgraded to 2.0 which may cause applications using the exact-match flag set to true
to fail to deploy. The solution is to set exact-match to false. JSF 2.0 is backwards compatible with previous versions and should not
cause any problems.


IDE and Java SE Development

Structure Pane Enhancements (11887639)

A couple of new enhancements in the structure pane were introduced, particular to assist when dealing with large, complex tree structures:

Pasting from Windows directly into JDeveloper running on hosted Linux via VNC (11842393)

When using JDeveloper through VNC Viewer, pasted data originating from the VNC client will not be available to the hosted JDeveloper process. To synchronize JDeveloper with the system clipboard, switch focus from JDeveloper to another application, and then back to JDeveloper again.


Password field disabled for keyboard entry on 64-bit Red Hat Linux

A JDK bug will sometimes prevent keyboard input into Swing password fields. You may be able to click in the field but you cannot enter a string or use navigation keys such as the Tab key. This occurs on 64-bit Red Hat Linux systems.

You may encounter this issue when you are using:

  1. Domain Configuration Wizard when logging into the Integrated WebLogic Server for the first time
  2. Standalone Domain Configuration Wizard (launched from Quickstart to configure a standalone WebLogic Server)
  3. ADF Model Tester (which prompts for a password when testing an application with ADF security enabled)
  4.  Create Database Connection dialog

The workaround is to issue the following setenv command before you launch the IDE or Quickstart.


setenv LC_ALL en_US

Change in Default for "Check for Externally Modified Files on Startup" setting

In previous releases, JDeveloper was configured by default to check the timestamp of files on disk for opened projects at startup.
If modifications are found, JDeveloper synchronizaes the project contents with the version that is on disk. For performance reasons,
the default setting for this option has been changed in this release.

With this setting off, it's possible for the contents in the JDeveloper project to be out of date with respect to files on disk if those files
have been modfied by another program. To refresh the project contents (you can select multiple projects at once in the navigator), use
the View > Refresh command.  Alternatively, you can modify the setting in Tools > Preferences, Environment tab by checking the option
to Check for Externally Modified Files on Startup.

If you migrate your IDE settings from a previous release, you will continue to have the same behavior as you are accustomed.


Web Applications

We do not currently support the use of the JSFC attribute with HTML tags.

Database Development

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


 Migrating .generate Files from JDeveloper 10.1.3 to JDeveloper PS3 (10385245)

The persistence format of .generate files changed between JDeveloper 10.1.3 and JDeveloper PS3, and if you migrate
an application that contains generate files from JDeveloper 10.1.3 to JDeveloper PS3 you need to force any .generate files
to be saved 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.



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_18The 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\

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

Upgrading a Application Server with JSF 2.0 Shared Libraries to run Applications

The ADF Runtime will be installed into a standalone application server by applying an Opatch bundle on top of a PS4 version of the Application Developer shiphome. In the event that additional patches are needed or desired in addition to the Sherman 11.1.2 patch (for example, if an additional patch is needed for another component in the Application Development Runtime shiphome), those patches will need to be installed separately.

Important Note: The patch is intended to be applied to an Application Developer shiphome only. Applying the patch to a different shiphome (for example SOA Suite or WebCenter) is not supported.


Key Installation steps for EXISTING Oracle WebLogic Server Users

  1. Ensure server is an 11g Release 1 Patch Set 4 ( Application Developer shiphome. Patch Set 4 itself will be available in both a "patchset" form as well as a "full" install. Customers using a version of Application Developer shiphome prior to Patch Set 4 will need to upgrade their environment to Patch Set 4 before installing Sherman 11.1.2. For more information see the Oracle Fusion Middleware Patching Guide.

  2. Download the Sherman 11.1.2 Opatch bundles and use the opatch tool to apply the patches.
    ADF patch  bug #12611176 and WebCenter patch bug#12556632

    Shutdown the target domain servers.

  3. Run the WLST "upgradeADF" command in offline mode.

  4. Restart the servers.


Key Installation steps for NEW Oracle WebLogic Server Users

  1. Download and install WLS 10.3.5 (CIE install).

  2. Download and install Application Developer (OUI install). For more information see the Oracle Fusion Middleware Installation Planning Guide.

  3. Run the Fusion Middleware Configuration wizard and create a new domain, or extend an existing domain, using the JRF + EM + OWSM domain template.

  4. Download the Sherman 11.1.2 Opatch bundles and use the opatch tool to apply the patches.
    ADF patch  bug #12611176 and WebCenter patch bug#12556632

    Shutdown the target domain servers.

  5. Run the WLST "upgradeADF" command in offline mode.

  6. Restart the servers.

Key Installation steps  for IBM WebSphere Application Server Users

  1. Download and install WebSphere if needed. For more information, see the Oracle Fusion Middleware Third-Party Application Server Guide and IBM WebSphere Application Server documentation.

  2. Download, install, and configure Application Developer (OUI install). For more information, see Oracle Fusion Middleware Installation Planning Guide.

  3. Download the Sherman 11.1.2 Opatch bundles and use the opatch tool to apply the patches.
    ADF patch  bug #12611176 and WebCenter patch bug#12556632

    Shutdown the servers.

  4. Run the wsadmin "upgradeADF" command in online mode while connected to the server.

  5. Restart the servers.

Install the Patch

  1. Install the patch. For WebLogic, install the script into the
    ORACLE_HOME/oracle_common/common/wlst directory. For WebSphere, install the script into the ORACLE_HOME/oracle_common/common/wsadmin directory.

  2. Run either the WLST or wsadmin shell and invoke the commands as described in the next section.

  3. Use the application server's administrative console to verify that the shared library is installed correctly on the server.

  4. Deploy JSF 1.2.9 and JSF 2.0 applications to validate that they work. Note that if an existing application explicitly specify that it requires an exact match against a JSF 1.2.x version, then you must match this version before running the application against the 11.1.2 shared library. This should not be a typical case.

  5. Validate the shared library using Enterprise Manager.

Run the Commands 

  1. For WebLogic, invoke the following command in WLST offlne mode.  For example:

    wls:/offline> upgradeADF('/scratch/jdoe/oracle/jdeveloper/system11.')
    Target Library "jsf#2.0@" to JRF "DefaultServer"

    Parameter 1 (Required) - DomainLocation - Domain to be upgraded
    Parameter 2 (Optional) - JSF Library Name. Defaults to jsf.
    Parameter 3 (Optional) - JSF Library Spec Version. Defaults to 2.0.
    Parameter 4 (Optional) - JSF Library Impl Version. Defaults to

  2. For WebSphere, invoke these commands in wsadmin online mode (i.e. when connected to the server). Note: you can obtain the SOAP port number from the deployment manager's portdef.props file.

    >  -conntype SOAP  -port  portnumber  -user username -password password
    > ADFAdmin.upgradeADF('DefaultCell', 'OracleCellFederatedNode', 'OracleAdminServer')

    Parameter 1 (Required) - Cell
    Parameter 2 (Required) - Node
    Parameter 3 (Required) - Server
    Parameter 4 (Optional) - JSF Library Name. Defaults to jsf.
    Parameter 5 (Optional) - JSF Library Spec Version. Defaults to 2.0.
    Parameter 6 (Optional) - JSF Library Impl Version. Defaults to




Web Services Development

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

TopLink DBWS Generation Fails with NPE (11665601)

The fix for this is available from ARU patch 13573106.

Running TopLink DBWS secured with OWSM policies that require a keystore fails (10229986)

It is not possible to run a Toplink database web service provider secured with an OWSM policy that requires a keystore. There is likely
to be a XML read error thrown from the OWSM layer on the server side. Though there is no workaround for this specific issue, securing
the provider service with a simple username token policy that does not rely on a keystore for credentials would make it work.

Policy not enforced on a provider service with no WSDL

For a web service provider with no WSDL associated with it, any policy attachments on it are not enforced by the server.  In order to warn the user from deploying such a service, JDeveloper puts up a warning on the code editor when such a scenario is detected. The workaround for this problem is to keep a WSDL for the provider service and attach it to the service using the 'wsdlLocation' annotation parameter.

Failure to PUT or POST to a Jersey REST Service co-located in a project with ADF components (12542672)

You might notice a "{{org.xml.sax.SAXNotRecognizedException: http://javax.xml.XMLConstants/feature/secure-processing}}" exception when using the PUT or POST operation on a Jersey resource that is co-located in an application that contains any ADF components or any project that overrides the default XML parser to use the one that is part of the XDK. This is caused by WLS bug 12543845 where an invalid configuration property is store and causes all further XML parser instances to fail.

The workaround is to disable the part of Jersey that sets this proper with a servlet init param:


This should only be applied if the user knows for sure they are using the XDK otherwise this will open up a possible security whole.

JAX-RPC web service design-time support now deprecated

With the deprecation of JAX-RPC in the Java EE 6 platform, this will be the last major JDeveloper release (ie the 11g release set) where the generation of a JAX-RPC style web service will be supported in the JDeveloper web service design time. Therefor, in the next major release set (currently scheduled to be 12c), the JAX-WS and JAX-RS standards will be the web service standards supported by the JDeveloper
web services design-time and there will be no support for the generation of web services that conform to the JAX-RPC standard.

Can't create data control metadata over web service method parameters and returns (12433980)

When creating a web service on an EJB session bean, you must manually update the parameter name and return name annotations with the type before generating the associated WSDL file to add to the project.

By default, the @WebParam name is set to "arg#", and the return type is not generated in the annotation. Before you generate the WSDL file, you must do the following for each method:


For example, say you created a web service method with the following annotation:

public Employee getManager(@WebParam(name = "arg0") Departments dept) {...}

You would need to manually edited the method to look like this:

public @WebResult(name="Employee") Employee getManager(@WebParam(name="Departments") Departments dept) {...}

Note that this workaround does not work with methods that have multiple parameters of the same type, or if the underlying artifacts
(EJB, XSD) are not local to the project.


java.lang.illegalstateexception: sslcontextimpl is not initialized after migration from PSx (12660729)

If you are upgrading from PS5 or another release of JDeveloper you may find exceptions of the following form when using code that accesses https connection or configures code that might access network connections.

java.lang.IllegalStateException: SSLContextImpl is not initialized
&nbsp;&nbsp;&nbsp;&nbsp; at
&nbsp;&nbsp;&nbsp;&nbsp; at
&nbsp;&nbsp;&nbsp;&nbsp; at
&nbsp;&nbsp;&nbsp;&nbsp; at
&nbsp;&nbsp;&nbsp;&nbsp; at

This is generally caused because the user has altered the default HTTPS settings, probably the trust store, to point to a certificate file that no longer exists. (In the cases we have seen this is because they point to the cacerts file from a previous install that has been removed)

You can resolve this problem by resetting the HTTPS settings in Tools->Preferences->Credentials->HTTPS Credentials->Default. A tool restart might be required.


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.

Team Productivity Center Issues

Changed API on WorkItemConnector interface retrieved (11930874)

Beginning in release, the following API on WorkItemConnector interface has been changed.

The previous API was:


public void updateDynamicModel(Map session, Map<String, WorkItemDef> existingModels)  throws ALMException;

The new API is now:

public String getDynamicModel(Map session, String currentModel)  throws ALMException;

Connector writers need to recompile the code so the connector can continue to work with JDeveloper.

Changed API to Bugzilla repository with REST API

Oracle Team Productivity Center's Bugzilla connector supports access to Bugzilla repository with REST API enabled with release If you have used Oracle Team Productivity Center's Bugzilla connector with earlier versions of Oracle JDeveloper, you need to update your Bugzilla server and enable the REST API.

For details, see the Mozilla wiki at

Bugzilla access through XML-RPC is no longer supported.

Seeded data remains in ENU jf JDeveloper runs in Japanese language

When using JDeveloper in the Japanese language, the seeded data remains in English. For example, in the Team Administration
dialog > Users tab, the status field shows its values in English: "Active" and "Inactive."

Hudson plugin duplicates changeset details to Team Productivity Center (12381649)

The Hudson plugin lets Team Productivity Center users create a relationship on a work item's Changes tab between that work item's checked-in files and related build information. Due to a bug in the Hudson plugin (HUDSON-8840), the changeset name returned to Team Productivity Center by Hudson is not correctly tied to the source control management (SCM) system's changeset/revision number. As a result, the details for the SCM's included files and the Hudson related builds are displayed on the work item's Changes tab as two separate entries -- one for Included Files and one for Related Builds.

CruiseControl test collector does not insert test results for duplicate test names (12614539)

If there are multiple tests with the same name, the CruiseControl test collector does not insert test results for subsequent tests using the same name.

As a workaround, prefix the test name with the class name being tested.

For example, if you have two classes that use the same test name, such as the testAccess() test that is generated for each class by the ADF Business Components Test Suite, you can prefix each test with the class name.

Source Control Management changeset information fails if work item info is not in the first line of the checkin comment (12617400)

Adding a checkin comment above the Team Productivity Center work item details on the source control management (SCM) commit dialog causes the work item information to be read incorrectly. As a result, the work item information is not tied to the work item, in either the Build Dashboard or the Work Item Changes tab in Team Productivity Center.

As a workaround, associate the work item with the checkin first. This puts the work item details (the repository name, the work item number, and the task name) in the checkin comments. Then you can add any checkin comments after the work item details in the SCM commit dialog.

You can then mouse over the comments on a change set to see the entire comment text, rather than having to scroll across the table.


WLS Hot Reload

This feature, enabled only in the Integrated WLS in JDeveloper, speeds up the development process by allowing the changes made
          to the project visible upon rebuild without deployment.

For JDeveloper deployments, the Fast-swap feature of WebLogic is disabled by default.  Fast-swap allows eligible class file changes to be visible in the application run-time by simply refreshing the browser.  See this WebLogic Fast-Swap document for more details.  Class file changes are copied to the running application when the source file is built.

Enabling Fast-swap:

The following are known limitations of running with Fast-swap enabled:
  1. When deploying Web Services, the generated WSDL file may contain additional entries for the Object class methods such as (9236022)
    <operation name="equals">
      <input message="tns:equals" />
      <output message="tns:equalsResponse" />

    It is important not to use WSDL's generated from the server in this mode when publishing WSDL's to third parties to consume. This will represent an incorrect version of the service and may in certain cases prevent the client from functioning properly. The extra methods may also not be secured properly which might imply some compliance problems depending on the back end data.

  2. On Windows, if an app is deployed with Fast Swap enabled, then if a class from a JAR library is being loaded and if that JAR file's URI contains a space, you get an error (11884533): Illegal character in opaque part at index 11: 
    zip:D:/With Space/Application77/lib/DependentLib.jar\!/dependentlib/DependentLibClass.class

    A workaround is to place the application or JAR file in a directory with a URI that does not contain spaces.


WLS Hot Reload does not reflect changes made to adfm.xml. You need to redeploy your application if following changes are made.

  1. Creating an Application Module in a new package. A new bc4j.xcfg file is created in the package and the entry added to adfm.xml.
  2. Creating a data control definition of any kind for the first time in a project. Creates a new DataControls.dcx file and is referenced by adfm.xml.
  3. Creating a new project dependency in the workspace (jdeveloper application). If the new project dependency has an adfm.xml of its own, i.e. it contains Business Logic Groups (BLG), shared application module, bean controls, or data binding registry, it will not get picked up. The .jpx, .dcx and .cpx files are referenced in adfm.xml and the adfm.xml in the dependent project will not get picked up.


Application Module failover can interfere with the passivation triggered from Hot Reload. It is recommended to disable Application Module failover when working in Hot Reload mode.

For example, a new view criteria is added to a view object to narrow the query result but same rows are returned. This is the expected behavior as Hot Reload saves your previous state and tries to restore your refreshed state with the same data. The query changes will
take effect in a new login session.

Hot Reload is turned on by default when the application is run in the Jdeveloper's integrated weblogic server. To implement the feature ADF runtime checks for modifications to any cached definitions at the beginning of a web request. Based on the size of the project it may slow down the performance of the application. Please note that this is not an issue when the application is deployed to an external weblogic server. If you don't plan to take advantage of the Hot Deploy feature it can be turned off by editing the Project Settings->Java EE Application->Integrated WLS commandline and appending the jvm property -Doracle.jdeveloper.adrs=false.



ADF Desktop Integration (ADFdi)

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

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. (6377073)
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 (12360953, 9718945)

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 work-around is to save the object and then re-open.

Sample issues:

Known Issues with ADFdi List of Values Components (8651633, 8651645)

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

Known Issues with SSL (7117108, 9536914)

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

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

Known Issues at design-time (9737702)

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

  1. Install the new ADFdi client
  2. Create a backup copy of the design-time version of your workbook
  3. Open the design-time version of your workbook
  4. Dismiss any error dialogs if the old client has been uninstalled
  5. When prompted to migrate, click "Yes"
  6. Test your workbook: review/adjust the column widths of your table's Changed and Flagged columns;
    review the runtime ribbon tab contents; adjust any labels as desired.
  7. Publish your workbook
  8. Repeat this process for each integrated workbook in your application
    Note: a migrated workbook can no longer be used with the old client.

ADF Faces and Data Visualization Runtime

IE8, IE9 note:   Compatibility View mode must be off.
For a listing of all supported browsers, see Supported Platforms section.

StringIndexOutOfBoundsException in (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-
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

If Active Data Service is enabled in an application, there are certain ADS pages (/adwwls/ 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/ or adw.jspx.

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:


User Specified Window Names

In this release we start to support user specified window names. A user can launch a window and give it a name, and we will continue
to use that name if it's valid. Currently the supported character set for window name is : [a-z][A-Z][0-9]_

Skinned Icons Resize (10058868)

Until recently there were limitations with skinning icons that -tr-rule-ref and -tr-inhibit were not supported. Further, the skin properties were not inherited from base skin for icon selectors. We fixed these limitations to make the icon selector behavior consistent with general skinning style selectors. Now that we inherit the skin properties for icons, if there were 'content' and other properties like 'width' and 'height' set, and you override just the 'content' property in your custom skin, you would inherit the 'width' and 'height' from the base skin. While this is a change in behavior, it is a change in right direction. If this behavior is not desirable, skinners can use -tr-inhibit to inhibit some properties or 'tr-inhibit: all' to inhibit all properties before overriding the 'content' property.

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.

RichText Editor Error Messages (11686814)

It is recommended that the application developer add a validation rule for situations where the Error Message returned by the RichText Editor would include the text contained in the RichText Editor and that text may be large enough to not be properly displayed by the browser.

Facelets Applications Will Lose State After Failover (12382285)

Due to the issue in Jthe SF reference implementation (2048), Facelets applications running in clustered environments will lose state after failover. End users experiencing error messages after faiover should be advised to refresh the page.

Facelets-Specific Region Child Creation Context Parameter

The af:region component implements a Facelets-specific optimization whereby the region's children are not created until the region itself is rendered. Deferring the cost of child creation for non-rendered regions can be a significant optimization, especially in cases where regions are hidden inside of af:showDetail, af:showDetailHeader or af:showDetailItem ancestors. This optimization is enabled by default but can be disabled by setting the "" context parameter to "immediate".



ADF DVT Graph and Gauge

ADF DVT Pivot Table

ADF DVT Pivot Filter Bar

ADF DVT Gantt Chart

ADF DVT Hierarchy Viewer

ADF DVT Geographic Map

ADF DVT Thematic Map

Severe warning converter when rendering pate (12399358)

When you view a facelets page which contains converters (af:convertNumber, af:convertDateTime and af:convertColor) in the Visual Editor, warnings are shown on the console and Log Messages pane. The messages are of the form "SEVERE: /view1.jsf @ 13,20 id="dte_16dddba" Unhandled by MetaTagHandler for type org.apache.myfaces.trinidadinternal.convert.NumberConverter". The messages do not impact design or runtime functionality and can be ignored.

JSF Upgraded to 2.0

The JSF version packaged in has been upgraded to 2.0 which may cause applications using the exact-match flag set to true to
fail to deploy. The solution is to set exact-match to false. JSF 2.0 is backwards compatible with previous versions and should not cause
any problems.


ADF Faces and Data Visualization Design Time

A new JDeveloper editor is available starting in for creating and editing ADF skin files. The core features include:

Applying an ADF Skin that Extends the Fusion Simple ADF Skin to a or Web Application

If you develop an ADF Skin that extends the new Fusion Simple family of skins (for example, fusionFx-simple-v1.desktop) that you want to apply to an or web application, you must also add the fusion-simple-skin.jar*  file to your web application. The fusion-simple-skin.jar file contains the Fusion Simple family of ADF skins that you extend for these releases ( and You download the fusion-simple-skin.jar file from the following:;&nbsp
For information about how to add this JAR file to your application, see the Importing ADF Skins from an ADF Library JAR section
in the Skin Editor's User Guide.

Component Palette Reorganization

The ADF Faces components in the component palette were reorganized into new accordions and display groups. This was done to assist users in locating and identifying components more efficiently and effectively by making the organization more predictable and usable. The reorganization will also accommodate the addition of new components in the future.

Support for Building Nested Templates

Previously, one was only able to utilize a single page template in their page (chosen during the creation of the page). Also, one was not able to include another page template while creating a page template definition. That restriction has been removed and a new Template item is now available in the component palette which can be DnD'ed onto either a page template definition or a regular page. A dialog will appear prompting the user to choose a page template to point to. With this new feature, the ability to nest page templates is now possible.

Conversion Support for ADF Faces Layout Components

The ability to convert between various ADF Faces layout components was reintroduced in (specifically, decorativeBox, group, panelAccordion, panelBorderLayout, panelBox, panelFormLayout, panelGroupLayout, panelHeader, panelList, panelSplitter, panelStretchLayout, panelTabbed, showDetailHeader, and toolbox). For cases that cannot be resolved algorithmically, a new Convert dialog will be shown to prompt the user for direction.

ADF DVT Databinding and Design Time

ADF Business Components

Duplicate View Instance Usages in an Application Module Definition Leads to Compiler Error (12413907)

Starting with JDeveloper, duplicate entries of view instances that appear in the application module .xml file, will be reported as an error during compilation. This is a new compiler behavior that is intended to prevent users from creating corrupt XML definitions. If you migrate an application into JDeveloper or later, the duplicate XML elements will fail to compile after migration has been completed. In this case, you will need to edit the XML definition to manually remove the duplicate entries and then continue to build the application. Duplicate view instance usages appear in the application module definition like this:



Using ADF Model Tester to test Application Module Deployed as an EJB Session Bean (11884503)

When you enable an application module to support EJB Session Bean, we no longer generate the Configuration for testing in integrated server. You can create the bc4j.xcfg entry for testing by following these steps:

  1. Select Run > Start Server Instance to start the integrated WebLogic server
  2. Select Project Properties... > Deployment and create a Business Components EJB Session Bean deployment profile
  3. Select "IntegratedWebLogicServer" in the Deploy to Connection dropdown
  4. Click Next > Finish

Now you can deploy the EJB Session Bean and select the new configuration (Type=EjbWls) to run the Tester.

ADF Swing

Building ADF Swing application has been deprecated in this release. It will be removed in the next release of JDeveloper.

Extension SDK

In this release the Extension framework as been changed. It is now based on an OSGi framework and extension written for previous
releases will not run out of the box in this new release. Please read the new Developers Guide for JDeveloper Extensions under
Help --> Table of Contents

Translation and Globalization Issues

Font Issue

When running Jdeveloper in Japanese Windows MUI machine, you may find some Japanese Character are displayed as square, it's caused
by the font used by Jdeveloper UI is not installed in the MUI env.

This font issue does not exist in Native Japanese Windows machine and Linux machine.

Oracle Help for the Web (OHW-RC)

11gR1-PS4 OHW help application fails to run after the user upgrades the Oracle Help system files from 11gR1-PS4 to 11gR2 (12572334)

The user must update and rebuild the OHW help application, because the configuration file has been updated in 11gR2. For more information about the configuration file, see "Understanding OHW Deployment" in the Oracle Fusion Middleware Developer's Guide for Oracle Help.

Follow these steps to update the OHW help application:

1. Copy the helpset files and the configuration files from the old OHW help application to the new OHW help application location.

2. Update the web.xml file and add the following servlet mapping information.

<\!-\- Route the OHW-RC resources through the resource servlet. \-->
&nbsp; <servlet-name>resources</servlet-name>
&nbsp; <url-pattern>/ohr/*</url-pattern>

The following example shows a sample web.xml

  <servlet-name>Faces Servlet</servlet-name>
  <servlet-name>Faces Servlet</servlet-name>
  <servlet-name>Faces Servlet</servlet-name>
<!-- Route the OHW-RC resources through the resource servlet. -->

<!-- configuration for product1 help front servlet -->

<!-- configuration for product2 help front servlet -->

<!-- servlet mappings for the OHW-RC front servlets -->
</servlet-mapping>D:/With Space/Applicat


<!-- OHW-RC servlet filter definition and mappings -->

  <servlet-name>Faces Servlet</servlet-name>


The user can now build and run the OHW help application.


Enterprise Manager Issues 

Delete metadata partition operation displays an ADF exception (12559266)

Deleting a metadata partition from a Metadata Repository home page, causes an ADF_FACES- error to be displayed in a popup.

Click the "ok" button to dismiss the ADF_FACES- error popup dialog. Click the "Cancel" button to dismiss the delete confirmation dialog too. If you click the "Ok" button, you will get a the popup with the "ADF_FACES-" error message again.  Instead, click the "Cancel" button to dismiss the delete confirmation dialog. 

The partition selected will have been deleted if there was no other error even though the partitions table in the home page does not reflect the deleted partition. The partitions table continues to display the partition that was selected for deletion. To refresh the partitions table contents, reload the page using the browser. Alternately revisit the Metadata Repository repository home page after visiting a different target home page.

Navigation using the browser back button does not work (12582730)

In Navigation between target home pages using your browser's back button does not work. Use buttons/links
in a page along with the left navigation tree to move between the pages.

Context sensitive help topics are not displayed in different pages (12582502)

1. In em.war file (inside em.ear) update web.xml to include the following servlet mapping:

<!-- Route the OHW-RC resources through the resource servlet, where resources is 
org.apache.myfaces.trinidad.webapp.ResourceServlet configured as shown in web.xml shown above. -->

2. Copy help pages from
oracle_common/modules/oracle.help_5.0/ to

3. Bounce the server and open the OHW help application again. It will work this time.




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.


Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065, USA

Worldwide Inquiries:
Fax 650.506.7200

Copyright © 1997,2009, 2010, 2011 Oracle and/or its affiliates.
All rights reserved.



Source Control Management changeset information fails if work item info is not in the first line of the checkin comment (12617400)

Adding a checkin comment above the Team Productivity Center work item details on the source control management (SCM) commit dialog causes the work item information to be read incorrectly. As a result, the work item information is not tied to the work item, in either the Build Dashboard or the Work Item Changes tab in Team Productivity Center.

As a workaround, associate the work item with the checkin first. This puts the work item details (the repository name, the work item number, and the task name) in the checkin comments. Then you can add any checkin comments after the work item details in the SCM commit dialog.

You can then mouse over the comments on a change set to see the entire comment text, rather than having to scroll across the table.

false ,,,,,,,,,,,,,,,,