This document contains a list of known issues (and, where applicable workarounds for those issues) for the following products:
For a list of new features in this release, see the What's New document on OTN.
This document describes known issues with the release. If and when new issues are discovered they will be added to this document. Please also use the JDeveloper community discussion forum and other community resources for questions and answers and to let us know what you think!
Please read the installation guide for details on system requirements and specific installation instructions for various platforms.
If you ran the printJarVersions.sh script in Unix/Linux and received "syntax error" and/or "command not found" errors, you need to run the dos2unix command on printJarVersions.sh. After you have done this, printJarVersions.sh should run without those errors.
When you install JDeveloper, a complete WebLogic Server environment is also installed for development, testing, and debugging purposes, also referred to as the JDeveloper Integrated WLS. In the event that it is necessary to apply patches to Integrated WLS, you can use either the SmartUpdate feature of WLS or Oracle Opatch depending on how the patch is provided from Oracle.
Linux workstations may have a process called SCIM running. This process may prevent entering a password in the Oracle Fusion Domain wizard or anywhere a JPasswordField occurs.
SCIM can also have an interaction when used in conjunction with VNC and VNCConfig which makes the keyboard temporarily unresponsive.
SCIM can also interfere with code insight as SCIM and code insight may share the same hot key (control+space).
Systems that have SCIM running will show SCIM processes when 'ps -A | grep scim' (without quotes) is typed in a terminal.
How to remove or disable SCIM is dependent on the version of Linux being used, possible ways include:
type: 'sudo yum remove scim' (without quotes) in a terminal, then log out/log-in
type: 'im-chooser' (without quotes) on the command line, select the Never use input methods option on the pop-up window, then click the Log out button. SCIM will be disabled at the next login.
Alternatively look for an 'Input Methods' item in preferences.
If JDeveloper is displayed on a remote X11 server, offscreen pixmaps should be disabled.
Either add the following to your command line:
or add the following to <Oracle Home>/jdeveloper/ide/bin/ide.conf
For further details about offscreen pixmaps, see the Java 2D troubleshooting guide at http://docs.oracle.com/javase/7/docs/webnotes/tsg/TSG-Desktop/html/java2d.html.
The OPatch bundles will continue to show in the update center even after they have been installed. Trying to install them again will not cause any harm. OPatch will simply ignore the install since the patch already exists.
The Spring extension bundle included on the JDeveloper DVD fails to load properly after installation. The error message is
SEVERE: Extension oracle.jdeveloper.spring.runner did not resolve properly and will not be loaded by the IDE. The workaround is to install the Spring extension from the online Update Center using Help > Check for Updates.
When running the "Entity" or "Entities from Tables" wizard, if you elect to attach an ID generator to each generated entity, you will need to manually configure the ID generator for the @SequenceGenerator or @TableGenerator options, depending on which one you select. For instructions, refer to the Javadoc generated into each entity class to obtain the SQL (DML and DDL) statements to execute.
Contexts and Dependency Injection (CDI) in Java EE 6 is not compatible with JavaServer Faces 2.1 (JSF 2.1). CDI with JSF currently only works with ADF Faces apps.
The JDBC-ODBC Bridge connection type is not recommended for making database connections, and Oracle does not support use of the JDBC-ODBC Bridge driver. For more information, see http://docs.oracle.com/javase/7/docs/technotes/guides/jdbc/bridge.html.
To connect to Oracle Database using OCI8 (thick connection), define the jar location using the system property jdbc.library. For example:
Creating a domain may take a long time on Linux machines with inadequate entropy. For more information, see Release Notes for Oracle WebLogic Server.
Shutting down IntegratedWebLogicServer may take more than 1 minute to ensure datasources have been written out. If you need to shut down the server fast you can use forced shutdown, but be aware that it kills the WebLogic domain process, running the risk of interrupting an active datasource and corrupting the data.
To use forced shutdown, go to Window > Application Servers > IntegratedWebLogicServer > Properties > Shutdown and choose "Shut Down Forcefully Always."
If you have created a custom ADF application using JDeveloper, (not a Fusion Web Application, which has a predefined template), check to see if you have the following properties and files in your application:
<listener> <listener-class>oracle.adf.share.weblogic.listeners.ADFApplicationStateListener</listener-class> </listener>
If any of these items are missing, you may receive an "Error 500: Internal Server Error" when you run the application. The first time you run this application, it may run correctly. But if you re-deploy and run this application again, you may get the error.
If you encounter log messages such as the following in an environment with two or more managed servers, make sure that the classpath does not contain JAR files named adf-pageflow-impl-1.0.jar or adf-pageflow-impl-n-n.jar. The classpath should only contain adf-pageflow-impl.jar.
The sample code illustrated in Example 23-7, "Attaching Policies to RESTful Web Service Clients Using Feature Classes," in "Developing and Securing Web Services," incorrectly uses the
com.sun.jersey.api.client.Client class. Instead, it must use the weblogic.jaxrs.api.client.Client class in order to support OWSM client policy attachment.
You cannot generate a RESTful client from a remote WADL that references a JSON schema due to the version of wadl.java.net library that is distributed with this JDeveloper release. The jsonschema2pojo library, on which it has a dependency, contains a bug that will cause a failure when attempting to generate a RESTful client if the WADL is not available on the local file system. The workaround is to copy the WADL and its resources locally and then generate the RESTful client from the local WADL.
For a web service provider with no WSDL associated with it, any policy attachments on it are not enforced by the server. To prevent users from deploying a Provider service without a WSDL, JDeveloper displays a warning in the code editor when this scenario is detected. The workaround for this problem is to maintain a WSDL for the Provider service and attach it to the service using the wsdlLocation annotation parameter.
Unless 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.
If you attempt to deploy a JAX-WS RI web service EAR or WAR file created using JDeveloper to Glassfish server, the deployment will fail.
To work around this issue, perform one of the following steps:
When working with CLOB domain attributes in your ViewImpl class, you must not use methods that have become deprecated due to changes in JDK 8 that resulted in removal of the sun.io.ByteToCharConverter class. When this class in JDK 8 was deprecated, it resulted in the following deprecated methods in classes of the oracle.jbo.domain and oracle.jbo.domain.generic packages.
(deprecated) public byte getStorageByteArray()
(deprecated) public byte getStorageByteArray()
When you need to work with Clob contents, instead use the following method from the above classes:
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.
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, RowviewRows, 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.
The application's adf-config.xml Do Failover option is set to true and in JDeveloper this option is set to disable for each Application Module. But when you deploy the application and use Enterprise Manager to configure the Business Components Application Module, the Failove State and checkbox is still enabled and unchecked. It should be disabled as indicated by adf-config.xml.
The reason is that after deployment, Enterprise Manager does not retrieve this value that was set in the application's adf-config.xml.
JDeveloper 12.1.3 and ADF has introduced a tightening security model for ADF BC Groovy expressions as a stepping stone for upcoming Oracle products. Oracle is progressively introducing this feature to reduce the burden on customers.
For any new ADF application, customers must set via the property inspector trustMode="true" for any ADF BC attributes or similar using a Groovy expression. Otherwise at runtime JBO-25152 will be raised.
For customers porting applications from previous releases of JDeveloper the trustMode will be set to true for existing Groovy expressions, though any new expressions still require developers explicitly set the trustMode.
The Configure ADF Security wizard displays a checkbox to enable Identity Governance Framework (IGF). The wizard displays this feature as unselected by default. However, when you select the checkbox no additional functionality is currently provided. The feature will be supported in a future release. For details about IGF, see the document Developing Applications with Identity Governance Framework in the Oracle 12c documentation library.
The invokeAction executable has been deprecated in Oracle ADF release 18.104.22.168.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.
The Java Management Extensions (JMX) data control is deprecated for Oracle ADF release 12.1.3, and the associated design-time tools will be removed from JDeveloper in a subsequent release.
In Releases 22.214.171.124.0 and 126.96.36.199.0 onwards, commit and rollback operations on shared data controls created outside a task flow transaction must be performed using ADF Model's commit and rollback binding actions.
ADF Model allows the creation of a "local" transaction context on data controls outside a transaction context started by a task flow. However, ADF Model does not allow a local transaction context to join the task flow's transaction. A task flow transaction will not commit or rollback changes on shared data controls created before the task flow transaction started.
For backward compatibility, the new default behavior in Releases 188.8.131.52.0 and 184.108.40.206.0 can be changed through configuration in Release 220.127.116.11.0. That is, you can enable the 11g R1 policy to allow the data control to join the new task flow transaction by setting the configuration property joinNewFrameTransaction to true. You set this property in the application's adf-config.xml file as shown in the following example:
With this configuration property, data controls that were created prior to the task flow transaction and have a local transaction context will join the transaction that the task flow starts. The local transaction contexts will be committed at the same time as the task flow transaction context. If you migrate an application from Releases 11g R1 to 18.104.22.168.0, the migration process makes the above configuration change in the adf-config.xml file for you.
In certain circumstances, re-executing this method may produced unexpected results. Workaround: perform a table download between invocations of UploadAllOrNothing.
Microsoft has announced that it will end support for .NET 4 (on Windows 7 and Windows 8) starting in January 2016. Microsoft recommends upgrading to version 4.5.2.
ADF Desktop Integration is compatible with .NET 4.5.2. Users may install it at any time. Future versions of ADF Desktop Integration may check for and install this version of the Microsoft .NET Framework.
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 already used by ADF Mobile and are now exposed in ADF.
As part of the new design time in 12.1.3 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 data-bound instances of deprecated tags is still supported.
The following table shows the mapping between the deprecated Graph tags and the new Charts tags:
|Old Tag (Deprecated)||New Tag|
In Chrome browser versions 34 and 35, the X Axis labels in chart are misaligned. This issue will be fixed in Chrome 36.