Oracle JDeveloper 10g (10.1.3): Desupported and Deprecated Features

July 2006

This document lists the features that will be desupported and deprecated in Oracle JDeveloper 10g (10.1.3) or later releases.

Desupported Features

This section lists the features that will no longer be available or supported in Oracle JDeveloper 10g (10.1.3) or later releases. All of the features listed are still supported in earlier versions of JDeveloper.

Web Services Modeling

Users should utilize the web services wizards, dialogs, and code editor to achieve the same functionality. Improved visualization of web services will be reintroduced in a later release.

JavaBeans Class Editor

JDeveloper now offers the ability to “Generate Accessors” directly from the code editor to generate your JavaBeans style getters and setters. Renaming and changing methods is now accomplished through the much more powerful refactoring menu, and creating new methods is now accomplished as a quick-fix when you invoke a nonexistent method from within the code editor. The Class Editor functionality is now available in several other areas throughout JDeveloper.

Entity Facade Support in ADF BC

You can still use Oracle ADF data binding against applications that are built using hand-written EJB Session Beans and EJB Entity Beans, or you can transition to using regular ADF Entity Objects instead.

Hosted Documentation

This affects only the ability to access hosted documentation from within JDeveloper--instead, use the local documentation automatically installed with JDeveloper. The local documentation now includes a revised Start page, cue cards, and dynamic help links. Updates to the local documentation can be distributed through the "Check for Updates" feature. The online web-accessible version of the documentation on OTN will remain available.

Designer Integration

The Designer integration features (which include the Designer Workarea connection and Designer ADF Business Components generator) are no longer provided with JDeveloper commencing with JDeveloper 10.1.3. The Designer integration features are still supported in JDeveloper 10.1.2. Forms and Designer customers transitioning to JDeveloper and ADF should visit the J2EE for Forms Developers site on OTN for more resources. Additionally, these customers should investigate the capabilities and services offered by JHeadstart and Oracle Consulting.

..............................................................................................................................................................................................

The following features were deprecated in Oracle JDeveloper 10g (9.0.5). They are desupported as of JDeveloper 10g (10.1.3). Click here for the original announcement in February 2004.

Data Web Beans and HTML Web Beans (JSP Pages)

The recommended approach for developing new databound JSP pages is to use ADF data binding with JavaServer Faces (JSF) components. Regular (non-JSF) JSP pages using ADF databinding with the JSTL tag library and standard EL expressions are also fully supported. If you add components to a new JSP page using ADF databinding and the Data Control Palette, you are automatically using the new, recommended approach. Note that you cannot mix deprecated and new-style tags in a single JSP page.

UIX JSP Tags, BC4J UIX JSP Tags and BC4J UIX XML Tags

This refers to UIX JSP tags (tags with the uix: prefix), BC4J UIX JSP tags (tags with the bc4juix: prefix) and BC4J UIX XML tags (tags with the bc4j: prefix). For developing new databound web pages with a rich set of components and a consistent look and feel we recommend using ADF databinding with the ADF Faces JSF component set instead.

Oracle SCM

With JDeveloper 10g (10.1.3) this feature will be installable through the “Check for Updates” functionality within JDeveloper. For more information please see the Oracle SCM Statement of Direction on OTN.

Deprecated Features

The features in this section are supported in Oracle JDeveloper 10g (10.1.3), but will be desupported in a future release of JDeveloper.

OJVM

OJVM is Oracle's Java VM implementation written to provide a richer set of features and improved performance for debugging and profiling than was possible with older versions of other VMs. Over time other VMS have introduced better capabilities for debugging and profiling, and Oracle is changing it's strategy to integrate with these VMS instead of maintaining our own.

OJVM will not be shipped in the next major release of JDeveloper. Customers should use Sun's HotSpot VM (client or server) instead for testing, debugging, and profiling application code. The following JDeveloper features will be effected by this change:

Debugger: Some JDeveloper debugger features are specific to OJVM. For example, the ability to Set Next Statement, and to view the heap. These features will be removed without replacement, but may be reintroduced in the future if and when such features could be implemented with HotSpot.

Profilers: The JDeveloper profilers in 10.1.3 and previous versions are specific to OJVM. For the next major release of JDeveloper, Oracle plans to provide rewritten profilers that work with HotSpot.

CodeCoach: CodeCoach will no longer be part of the JDeveloper product in the next major release. Many of the results generated by CodeCoach are already reported in real time by the audit and metrics features of JDeveloper. Some CodeCoach results (such as Array usage information) will not have a replacement.

UIX

The new "ADF Faces" JSF component set, which is an evolution of the original UIX technology, but now fully compliant with the JSF specification, is now the preferred thin client component development technology with JDeveloper moving forward. ADF UIX will, however, continue to be supported but will no longer be delivered as part of JDeveloper 10g (10.1.3). Click here for more information on UIX, ADF Faces and JDeveloper 10g (10.1.3), and here for information about the ADF UIX roadmap to ADF Faces with details on migration.

Business Components Data Tags (JSP Pages)

Business Components data tags (tags with the jbo: prefix) are supported in JDeveloper 10g (10.1.3) for the maintenance of existing applications, with the following restrictions:

·         The data tags appear in the component palette only when the current project contains a web.xml file with an entry for datatags.jar (this is the case for all existing data tags projects).

·         While basic tag insight works for tag and attribute names, Business Components-specific property value insight is no longer provided.

·         There are no longer pop-up component dialogs when adding new data tags from the component palette; tag attributes can be changed using the property inspector.

·         Migration of existing applications containing these tags is supported only from JDeveloper 10g (10.1.2). If you want to migrate a data tags application from an earlier version of JDeveloper to JDeveloper 10g (10.1.3), you must first open your application in JDeveloper 10.1.2, then open it in JDeveloper 10.1.3.

The recommended approach for developing new databound JSP pages is to use ADF data binding with JavaServer Faces (JSF) components. Regular (non-JSF) JSP pages using ADF databinding with the JSTL tag library and standard EL expressions are also fully supported. If you add components to a new JSP page using ADF databinding and the Data Control Palette, you are automatically using the new, recommended approach. Note that you cannot mix deprecated and new-style tags in a single JSP page.