Oracle JDeveloper 12c (12.1.2/12.1.3) Desupported and Deprecated Features

This document lists the features that have been desupported or deprecated in Oracle JDeveloper 12c (12.1.2/12.1.3)

Desupported Features for JDeveloper 12c

Desupported features are functionality that has been removed in this version. You may still be entitled to support (based on your Oracle Support contract) for the feature in the previous JDeveloper version prior to the feature's removal.

EJB 2.1

EJB 2.1 technology has been replaced with more recent versions, namely EJB 3.0 and 3.1.

Deprecated in Version: 11.1.2
Removed in Version: 12.1.2
Replacement Feature/Migration Plan: EJB 3.0, EJB 3.1

JAX-RPC

JAX-RPC is no longer supported in the Java EE stack. Superseded by JAX-WS and JAX-RS standards.

Deprecated in Version: 11.1.2
Removed in Version: 12.1.2
Replacement Feature/Migration Plan: JAX-WS, JAX-RS

Serena Dimensions Integration

Our research indicates a continued consolidation of version control systems toward open source options, namely git, Subversion, and (to a lesser degree) CVS. We are focusing on the version control systems that our customers are using most frequently.

Deprecated in Version: 11.1.2
Removed in Version: 12.1.2
Replacement Feature/Migration Plan: Suggest using an open source version control system (git, Subversion, CVS), or else invoke versioning commands directly from the client tool provided by the vendor.

ClearCase Integration

Deprecated in Version: 12.1.2
Removed in Version: 12.1.3
Replacement Feature/Migration Plan: Suggest using an open source version control system (git, Subversion, CVS), or else invoke versioning commands directly from the client tool provided by the vendor.

JBO Datatags

JBO Datatags (tags with the jbo: prefix) were desupported in 10g. As of 12.1.2, the runtime support for these tags has been removed.

Deprecated in Version: 9.0.4
Removed in Version: 12.1.2
Replacement Feature/Migration Plan: ADF databinding with the Web Application stack (ADF Faces + ADF Controller)

DVT Flash Rendering

Many of the DVT components are highly visual and interactive. One common way of supporting these controls across browsers in the past has been by rendering the components to Flash. With Flash support now lacking on key browsers and mobile platforms, and with ubiquitous browser support for the necessary HTML5 features for our components, we have removed runtime support for generating Flash output for DVT components.

Deprecated in Version: 12.1.2
Removed in Version: 12.1.3
Replacement Feature/Migration Plan: HTML5 rendering

ADF Mobile

ADF Mobile is superseded by a new product offering called Mobile Application Framework (MAF). MAF 2.0 was released in June 2014 as an extension on JDeveloper 12.1.3.

Deprecated in Version: 11.1.2.4
Removed in Version: 12.1.2
Replacement Feature/Migration Plan: Mobile Application Framework (MAF). When an ADF Mobile application is opened in JDeveloper 12.1.3 with the MAF extension installed, the application will be migrated to MAF.

Deprecated Features for JDeveloper 12c

Deprecated features are still supported in JDeveloper 12c under the appropriate Oracle Support contract. However, we do not plan to make future enhancements to deprecated functionality, and the affected feature may be removed in a future release. We strongly recommend customers to migrate to replacement functionality and to not start any new work with deprecated features.

Struts Runtime

Web technologies evolve at a frenetic pace. We introduced Struts support in JDeveloper 9.0.4 in 2002. In the 12 years since, we have seen many innovations and improvements in controller technology for web applications. Struts design-time was removed in 11.1.1 along with the introduction of ADF Controller to supplement the JSF page navigation. We plan to remove the Struts runtime in a future release.

Deprecated starting from Version: 10.1.3
Replacement Feature/Migration Plan: Web Application stack (ADF Faces + ADF Controller)

ADF Swing

Desktop, or client-server, architectures for database-bound applications have been steadily falling out of favor for years. We believe that the needs of the vast majority of JDeveloper/ADF users are better met by focusing on the Web Application stack (ADF Faces + ADF Controller).

Deprecated starting from Version: 11.1.2
Replacement Feature/Migration Plan: Web Application stack (ADF Faces + ADF Controller)

ADF BC - Three tier Application Module configuration using EJB

Used primarily as an option for ADF Swing, and is based on an old EJB stack (2.1). In this architecture a Java application runs on a client and makes calls to ADF BC resources exposed as EJB on an application server tier (which in turn accesses data from a database). EJB 2.1 RMI protocols have effectively been replaced by more open web services standards.

Deprecated starting from Version: 11.1.2
Replacement Feature/Migration Plan: Web Application stack (ADF Faces + ADF Controller). For use cases requiring a middle tier with remote clients, customers may also wish to consider using ADF Business Components exposed as REST or SOAP web services.

XSQL

Analysis indicates that the design time features for XSQL are seldom used. Therefore, we are removing the design-time elements, while the runtime support remains intact.

Deprecated starting from Version: 12.1.2
Replacement Feature/Migration Plan: XSQL can be hand coded with no support from the framework.

All Fusion Skin Families: fusion-base, fusionFx-simple, fusion-11.1.1.3.0, and fusionFx skin families

A more recent and modern version of our look and feel has been created, Skyros. The new skin leverages CSS3 functionality to make it lighter weight, faster, and easier to customize.

Deprecated starting from Version: 12.1.3
Replacement Feature/Migration Plan: Skyros skin family is the replacement for these skin families. Skyros is the default skin for all newly created applications in 12.1.2.0 and 12.1.3.0. Do not build new applications with the fusion skin families. For new applications starting in 12.2.1, users should also consider the cross-platform Alta skin.

Team Productivity Center, TPC Extension, TPC Connectors

Oracle is heavily invested in cloud infrastructure. The tools development team has been hard at work delivering development tools and lifecycle automation functionality to Oracle Public Cloud as part of the Developer Cloud Service. This has significant overlap with the functionality provided by Team Productivity Center, which will be discontinued as a result.

Deprecated starting from Version: 12.1.3
Replacement Feature/Migration Plan: Developer Cloud Service with improved direct integration with JDeveloper expected in future releases.

JPublisher Integration

JDeveloper integrates with JPublisher functionality to generate Web Service APIs for database objects as well as to generate Java code to access database objects. With improved options for generating Web Services (TopLink WS or Oracle Rest Data Services (ORDS)), and with reduced demand for generation of Java code from Database objects, JDeveloper intends to deprecate the out-of-the-box integration with JPublisher.

Deprecated starting from Version: 12.1.3
Replacement Feature/Migration Plan: Web Services API generation from database objects has been replaced with equivalent TopLink Web Services functionality in JDeveloper 12.1.2, or utilize Web Service publication with Oracle REST Data Services (ORDS). Java code generation has no replacement. Customers can manually write Java (JDBC) Code, or use an object-relational mapping solution such as ADF Business Components or TopLink.

SQLJ Integration

JDeveloper provides support for editing, compiling/precompiling, and debugging SQLJ. Analysis has indicated low adoption of SQLJ features within JDeveloper.

Deprecated starting from Version: 12.1.3
Replacement Feature/Migration Plan: No replacement. Customers can manually write Java (JDBC) Code, or use an object-relational mapping solution such as ADF Business Components or TopLink.