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

In earlier versions of JDeveloper the ADF Business Components Entity Object editor contained panels labeled Publish and Subscribe, which provided a way to declaratively create local events that were published and handled within the same entity object. This feature has been removed in 11g; developers may wish to implement their own event handling code, or simply use Java method calls instead of local events.

Note that existing applications using these events will continue to work when migrated to JDeveloper 11g.

ADF Faces Telnet Renderer

ADF no longer provides a render kit for telnet devices.

10g ADF Faces Components

The ADF Faces component libraries supported in ADF 10g have been desupported and replaced by the Apache MyFaces Trinidad Components. When an application built with the 10g components is opened in JDeveloper 11g, all of the ADF Faces components will be automatically migrated to the equivalent Trinidad components. You can also use the Trinidad components to build new applications; or you may wish to use the new ADF Faces Rich Client components.

For more information on migrating a 10.1.3 ADF Faces application to 11g, please see the document Migrating the 10.1.3 SRDemo Sample to 11g.

UIX

The ADF UIX components were deprecated in JDeveloper 10g ((original announcement) and are no longer supported in 11g; ADF Faces is now the recommended thin client component development technology.

Click here for more information on UIX, ADF Faces and JDeveloper, and here for information about the ADF UIX roadmap to ADF Faces with details on migration.

EJB 2.0

JDeveloper 11g does not support EJB version 2.0; EJB 2.1 and EJB 3.0 are still supported.

J2EE 1.3 Web Services

JDeveloper 11g does not support development of J2EE 1.3 Web Services. These Oracle proprietary web services are superseded by JAX-RPC and JAX-WS support.

Deployment to OC4J

JDeveloper 11g does not support deployment of applications to any version of OC4J. Please see the document Application Servers Supported by JDeveloper for details of the application servers supported by JDeveloper 11g.

ADF Installer

There is no longer an ADF Installer utility for ADF 11g. Installing JDeveloper 11g Studio automatically installs Oracle WebLogic Server and creates a domain that is configured to run ADF; you can also use the JDeveloper 11g installer to configure an existing Oracle WebLogic installation to run ADF applications.

For other supported application servers, we will at some point in the future publish instructions for installing the ADF runtime libraries.

OJVM

OJVM was 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 its strategy to integrate with these VMs instead of maintaining our own.

OJVM was deprecated in JDeveloper 10.1.3 (original announcement) and has been removed in JDeveloper 11g. You should use Sun's HotSpot VM (client or server) instead for testing, debugging, and profiling application code. The following JDeveloper features are effected by this change:

• Debugger: The ability to Set Next Statement, which was specific to OJVM, has been removed. This feature may be reintroduced in the future if and when such features can be implemented with HotSpot.
• Profilers: The JDeveloper profilers in 10.1.3 and previous versions were specific to OJVM. JDeveloper 11g has a functionally equivalent CPU profiler and Memory profiler working on JVMTI (a standard API implemented by Sun's JVM). The event profiler has been removed.
• CodeCoach: CodeCoach is no longer part of the JDeveloper product. 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) have not been replaced.

In ADF versions before JDeveloper 11, the ADF security framework stored its authorization information in the bindings (pageDef file). developers used the context menu to open the authorization editor to define a user role to privilege mapping. In JDeveloper 11, no security related data is written to the bindings. The change has the advantage that security administration now is fully decoupled from application development.  A new policy editor has been added that allows application developers to secure ADF pages and taskflows with permissions stored in the local policy file. UI component security will be enforced through a new ExpressionLanguage string set that check a given permission for the authenticated user.

The features in this section are supported in Oracle JDeveloper 11g (11.1.1.0.0), but may be desupported in a future release of JDeveloper.

Business Components data tags (tags with the jbo: prefix) are supported in JDeveloper 11g (1.1.1.0.0) 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.3). If you want to migrate a data tags application from an earlier version of JDeveloper to JDeveloper 10g, you must first open your application in JDeveloper 10.1.3, then open it in JDeveloper 11g.

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.

 Web Service policy has migrated to the OWSM infrastructure in release 11. New developments should use this security stack. The 10.1.3 style container based security descriptors and API are still supported in release 11, but are expected to be desupported in a future release.

In ADF versions before JDeveloper 11, the ADF security framework stored its authorization information in the bindings (pageDef file). developers used the context menu to open the authorization editor to define a user role to privilege mapping. In JDeveloper 11, no security related data is written to the bindings. The change has the advantage that security administration now is fully decoupled from application development.  A new policy editor has been added that allows application developers to secure ADF pages and taskflows with permissions stored in the local policy file. UI component security will be enforced through a new ExpressionLanguage string set that check a given permission for the authenticated user.

You should avoid using the following simple graph tags which are likely to be desupported in a future release. Instead, please use Advanced Graph <dvt:graph> tag.

• <dvt:dualYBarGraph>
• <dvt:stackedBarGraph>
• <dvt:dualYLineGraph>
• <dvt:dualYComboGraph>
• <dvt:horizontalStackedBarGraph>
• <dvt:stockCandleGraph>