| Oracle® Cloud Using Oracle Java Cloud Service Release 12.2 Part Number E27039-02 |
|
|
PDF · Mobi · ePub |
This section describes supported and unsupported capabilities for Java Cloud Service. It supplements the explanations in Chapter 4, "Developing Applications for Oracle Java Cloud Service".
Java Cloud Service supports the deployment of the following types of applications:
Web Application Archive (WAR) or Enterprise Archive (EAR) deployment. Note all supported applications must be deployed through a WAR file or an EAR file (which can contain multiple WAR or JAR files).
Tip:
The class loader behavior of EAR archives when deployed to a Java Cloud Service is the same as that of WebLogic Server as described in "Understanding WebLogic Server Application Classloading" in Oracle Fusion Middleware Upgrade Guide for Oracle WebLogic Server.Applications using Servlet 2.5, JavaServer Pages (JSP) 2.1, Java Server Faces (JSF) release 1.2 and release 2.0.
Use of web.xml, weblogic.xml deployment descriptors and related annotations is supported.
Applications using Java API for XML web Services (JAX-WS) 2.1 based web services. Use of webservices.xml, weblogic-webservices.xml deployment descriptors and related annotations is supported.
Applications providing REST-based APIs through Java API for RESTful web services (JAX-RS) 1.1 and Jersey 1.9 annotations are supported.
Enterprise Java Beans (EJB) Containers:
Applications using EJB 2.1 and EJB 3.0 specifications. Use of ejb-jar.xml, weblogic-ejb-jar.xml and related annotations is supported with the following exceptions:
Only local EJB invocations are supported, specifically, the client code invoking an EJB application's interface must be either within the same deployment archive as the EJB implementation code itself or within a deployment archive that is deployed to the same Java Cloud Service instance.
EJB 2.x Entity Beans are not supported.
Applications using Java Persistence API (JPA) 2.0 specifications and use of JPA persistence.xml elements with EclipseLink 2.1.3 specific extensions.
Direct use of Java Database Connectivity (JDBC) 4.0 APIs as described in "WebLogic Server 12.1.1 Compatibility with Previous Releases" in Oracle Fusion Middleware Upgrade Guide for Oracle WebLogic Serverr.
Use of Oracle Database 11g compatible SQL statements.
JDBC Data Sources provisioned within a Java Cloud Service instance upon association with a Database Cloud Service instance will be XA-enabled JDBC data sources.
Java Platform, Standard Edition (SE) 1.6 APIs:
Applications can use the set of Java SE 1.6 public APIs as long as they pass the Java Cloud Service whitelist tool and that their use is inline with Java EE best practices. See "About Java Cloud Service Whitelist".
Use of other Java EE 5 and 6 specifications as described in Table A-1.
Tip:
Some Java EE specifications in this section relate purely to the underlying Java EE container environment and are irrelevant to the actual Java EE deployment archives and how they are developed (for example, Java Authentication and Authorization Service (JaaS)). Although these specifications are supported, they are not listed here.Table A-1 Other Java Cloud Service Supported Application Types
| Supported Specification | Supported Version |
|---|---|
|
JavaServer Pages Standard Tag Library (JSTL) |
1.2 |
|
Java Data Base Connectivity (JDBC) |
4.0 |
|
Java Persistence API |
2.0 |
|
Web Services Metadata for the Java Platform |
2.0 |
|
Java Naming and Directory Interface Specification (JNDI) |
1.2 |
|
Java Transaction API (JTA) |
1.1 |
|
Streaming API for XML (StAX) |
1.0 |
|
SOAP with Attachments API for Java (SAAJ) |
1.3 |
|
JavaBeans Activation Framework Specification (JAF) |
1.1 |
|
Java API for XML Processing (JAXP) |
1.3 |
|
Java Management Extensions (JMX) Note: JMX is only supported for exposure of MBeans within a deployment archive and access to these MBeans from the deployment archive itself or other archives deployed to the same Java Cloud Service instance. |
1.2 |
|
Java API for XML-based Web Services (JAX-WS) |
2.1 |
|
Java API for RESTful Web Services (JAX-RS) |
1.1 |
|
Java Architecture for XML Binding (JAXB) |
2.0 |
Other public WebLogic Server 10.3.6 APIs and capabilities as described in Table A-2.
Table A-2 Supported Public WebLogic Server 10.3.6 APIs and Capabilities
| API | Description |
|---|---|
|
|
Used for internal (non-catalogue) WebLogic server logging |
|
|
For applications using custom WebLogic Server specific tags |
|
|
Response caching servlet filter |
|
|
Used for implementation of application lifecycle listeners |
|
|
Public I18N APIs and logging |
|
|
Public I18N APIs and logging |
|
|
For Java Naming and Directory Interface (JNDI) lookup within WLS JNDI tree |
|
|
WebLogic specific extensions to JAX-WS for supporting WS-* |
|
|
For annotations based servlet descriptions |
|
|
API used for direct JTA interaction |
Java Cloud Service does not support:
Any API deprecated in WebLogic Server release 10.3.6 or lower.
Any API deprecated in ADF release 11.1.1.6 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-3. The following table includes workarounds where applicable.
Table A-3 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 "Understanding On-Premise and Java Cloud Service Portability". |
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:
|
Not applicable. |
|
Application deployment archives that have a size of more than 95MB |
Not applicable. |
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-4.
Table A-4 Unsupported WebLogic Server 10.3.6 APIs and Capabilities
| Unsupported WebLogic Server Capabilities | Description/Rationale |
|---|---|
|
weblogic.wtc.* |
Tux integration is not supported. |
|
com.bea.logging |
Deprecated logging API. |
|
com.bea.httppubsub |
Not supported. |
|
com.bea.security.* |
All security in Oracle Cloud is handled at the identity management level. No custom security provider or model is supported. |
|
commonj.* |
Oracle Cloud does not support commonJ timers and work managers. |
|
weblogic.apache.* |
Deprecated and replaced by |
|
weblogic.webservice.* |
Deprecated WebLogic Server 8.1 web services features. |
|
weblogic.cluster.* |
Do not expose WebLogic Server clustering (including the Singleton service) at the Java Cloud Service level. |
|
weblogic.connector.* |
Java Cloud Service does not support JCA. |
|
weblogic.deploy.* |
Deployment must be performed through Java Cloud Service specific interfaces. |
|
weblogic.management.* |
Do not expose the WLS JMX tree at Java Cloud Service level. |
|
weblogic.rmi.* |
Java Cloud Service does not support Java Remote Method Invocation (Java RMI) calls. |
|
weblogic.security.* |
All security is handled at the Oracle Cloud identity management level. No custom security provider or model is supported. |
|
weblogic.time.* |
Deprecated and not supported at Java Cloud Service level. |
|
weblogic.uddi.* |
Deprecated in previous version of WebLogic. |
|
weblogic.workarea.* |
Deprecated in previous version of WebLogic. |
|
weblogic.xml.* |
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. |