Oracle JDeveloper 10g: Desupported and Deprecated Features

February 2004

This document lists the features that will be desupported in JDeveloper 10g (9.0.5) or later releases. All of the features listed are still supported in earlier versions of JDeveloper.

Desupported Features

This section lists the features that will no longer be available or supported in JDeveloper 10g.

Data-Aware Controls (DAC)

Data-Aware Controls design time features were desupported in JDeveloper 9.0.2, when JClient became the recommended approach to building databound Swing-based applications. In JDeveloper 10g, the DAC runtime libraries will also be removed and desupported.

For more details about JClient, and migrating from DAC to JClient, please see the Java Client Statement of Direction.

Deployment of Business Components to the VisiBroker ORB

Due to API changes to JDK 1.4, the VisiBroker 4.x ORB will not interoperate with JDK 1.4 and newer releases. As an alternative, you should use web module or EJB Session Bean deployment. The JDeveloper online documentation describes the available deployment options for Business Components.

Deployment of Business Components in an Oracle Database

JDeveloper 10g will no longer support deployment of ADF Business Components (BC4J) in an Oracle Database. This includes deployment of Business Components in an Oracle Database as:

• EJB Session Beans
• CORBA objects
• Java stored procedures

If you are running EJB session beans in the database, we recommend you migrate them to OC4J. If you are running Business Components as a Java stored procedure, we recommend you select a different deployment configuration. The JDeveloper online documentation describes the available deployment options for Business Components.

Note that JDeveloper 10g continues to support deployment of non-framework classes as Java stored procedures, and calling PL/SQL and Java stored procedures from Business Components.

Generating Java CORBA Files from an IDL Definition

JDeveloper 10g will no longer support the creation of IDL files, or the generation of Java CORBA files from an IDL definition.

Features to be Desupported in a Future Release

The features in this section are supported in JDeveloper 10g (9.0.5), but will be desupported in the next major release of JDeveloper.

SQLJ

SQLJ development will no longer be supported in the next major release of JDeveloper; this follows Oracle's announcement that SQLJ will be desupported in all product versions, effective 31st December 2005.

For more information about SQLJ desupport, please see the SQLJ Obsolescence and Desupport Notice, available on Metalink.

Deprecated Features

The following features are deprecated in JDeveloper 10g. They are still supported, but are not recommended for new projects. They are likely to be desupported in a future release of JDeveloper.

Data Web Beans and HTML Web Beans (JSP Pages)

JSP Pages containing Data Web Beans and HTML Web Beans are still supported in JDeveloper 10g; you can run pages built in JDeveloper 9.0.3, and add new components to them. However, the recommended approach for developing new databound JSP pages in JDeveloper 10g is to use the JSTL and ADF tags that are available in the Data Control Palette.

Business Components Data Tags (JSP Pages)

Business Components data tags (tags with the jbo: prefix) are still supported in JDeveloper 10g. You can run existing pages containing these tags, and you can add new Business Components data tags to your pages from the component palette. The recommended approach for developing new databound JSP pages is to use Expression Language (EL) which is supported by the JavaServer Pages Standard Tag Library (JSTL) for JSP 1.2.

The new EL and ADF tags can be used to access business services created with EJB, JavaBeans, TopLink and Web Services, as well as ADF Business Components. If you add components to a new JSP page using ADF databinding and the new Data Control Palette, you are automatically using the new, recommended tags. 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

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) are still supported in JDeveloper 10g. You can run existing pages containing these tags, and you can add new tags to your pages from the component palette. However the recommended approach for developing new UIX pages is to use UIX XML; and to create databound UIX pages the recommended approach is to use Expression Language (EL) in your UIX XML pages.

If you add components to a new UIX page using ADF databinding and the new Data Control Palette, you are automatically using the new, recommended tags. Note that you cannot mix deprecated and new-style tags in a single page.