Oracle Cloud Learning Center

A Java Cloud Service Deprecated Features and APIs

This button toggles the Table of Contents floating window


This section provides documentation about deprecated and unsupported features and APIs for Oracle Java Cloud Service for Oracle Cloud.


About the Java Cloud Service Deprecation Policy

The following describes the deprecation policy for Java Cloud Service:

  • All APIs marked as deprecated in Javadoc for WebLogic Server release 10.3.6 and ADF release are deprecated for the Java Cloud Service. See:
  • As a general rule, APIs that are marked as deprecated for Java Cloud Service in a specific version of the product, will be fully removed in the next major product update.

Unsupported Features and APIs

Java Cloud Service does not support:

  • Any API deprecated in WebLogic Server release 10.3.6 or lower.

  • Any API deprecated in ADF release or lower.

  • In addition to the areas detected by the Java Cloud Service whitelist, Java Cloud Service does not support the features and capabilities listed in Table A-1. The following table includes workarounds where applicable.

    Table A-1 Java Cloud Service Unsupported Features

    Unsupported Features Alternative

    Direct JAR deployment.

    Embed JAR in EAR.

    WebLogic Server shared libraries, deployments, and references except for references to libraries pre-defined in Java Cloud Service as described in Creating an On-Premise Environment That Is Comparable to a Java Cloud Service Instance.

    Embed shared library deployment archive within the referencing EAR/WAR file.

    Java EE Connector Architecture (JCA) Container - RAR deployments.

    Not applicable.

    Java Message Service (JMS) Services. Any application which has JMS dependencies, including use of WebLogic Server application scoped JMS modules.

    Not applicable.

    JAX-RPC-based web services.

    Convert to JAX-WS web services.

    Applications exposing or invoking asynchronous web services.

    Not applicable.

    Use of WS-* specifications other than WS-Security (through OWSM policies).

    Not applicable.

    Remote invocations with a transport protocol other than HTTPS (including plain text HTTP).

    Not applicable.

    Coherence applications, managed or used through WebLogic Server ActiveCache.

    Not applicable.

    Direct usage of any JRF API components other than ADF (for example, the direct use of Oracle Platform Security Services (OPSS) and ODL APIs).

    Not applicable.

    Direct use of Oracle JDBC Driver APIs.

    Not applicable.

    Use of SQL statements specific to a database instance other than Oracle Database 11g (11.2).

    Convert application to use Oracle Database.

    JavaMail API specification.

    Not applicable.

    Direct modification of the Java command line parameters including for the specification of system properties.

    Use web.xml context parameters or set system properties programmatically. See context-param in Oracle Fusion Middleware Developing Web Applications, Servlets, and JSPs for Oracle WebLogic Server.

    Application scoped JDBC modules.

    Modify application to use the system scoped data source created through the database association.

    Runtime OWSM policy attachments

    Policies must be attached at design time.

    Setting of operating system environment variables, Java system properties, or JVM/Server command line parameters.

    Dependencies on these variables would need to be brought into the application deployment archive (for example, the packaging of a properties.xml file and reading of the information from it).

    File system access by deployed applications.

    Not yet available.

    EJB 2.x Entity Beans.

    EJB 3.0 and JPA.

    The following ADF features:

    • ADF Desktop Integration

    • ADF mBeans

    • ADF seeded customizations or cross-session personalization (MDS)

    • ADF Mobile

    • ADF Active Data Services

    • ADF Business Components services interfaces (web services) or events

    • ADF Data Controls for BI, Essbase, BAM, and JMX

    Not applicable.

    Application deployment archives that have a size of more than 95MB.

    Not applicable.

    All sun.* packages in the Java SDK, including sun.misc.BASE64Encoder, are not supported. The sun.* packages are a security risk because they are internal-only, and so are not part of the public API.

    Alternative options for common encoders that have similar functionality are:

    In addition, Oracle Java Cloud Service does not support the use of the public WebLogic Server 10.3.6 APIs and capabilities as described in Table A-2.

    Table A-2 Unsupported WebLogic Server 10.3.6 APIs and Capabilities

    Unsupported WebLogic Server Capabilities Description/Rationale*

    Tux integration is not supported.


    Deprecated logging API.


    Not supported.*

    All security in Oracle Cloud is handled at the identity management level. No custom security provider or model is supported.


    Oracle Cloud does not support commonJ timers and work managers.


    Deprecated and replaced by org.apache.html.dom.


    Deprecated WebLogic Server 8.1 web services features.


    Do not expose WebLogic Server clustering (including the Singleton service) at the Java Cloud Service level.


    Java Cloud Service does not support JCA.


    Deployment must be performed through Java Cloud Service specific interfaces.*

    Do not expose the WLS JMX tree at Java Cloud Service level.


    Java Cloud Service does not support Java Remote Method Invocation (Java RMI) calls.*

    All security is handled at the Oracle Cloud identity management level. No custom security provider or model is supported.


    Deprecated and not supported at Java Cloud Service level.


    Deprecated in previous version of WebLogic.


    Deprecated in previous version of WebLogic.


    Some deprecated, some are security-related, some have more common use with external frameworks.

    .NET and C APIs for JMS

    Java Cloud Service does not support JMS or C or .NET clients.

Previous Page Next Page