diff --git a/14.1.2-0-0-SNAPSHOT/docs/main/config.js b/14.1.2-0-0-SNAPSHOT/docs/main/config.js index fa159ef2934a3..67438bda717c1 100644 --- a/14.1.2-0-0-SNAPSHOT/docs/main/config.js +++ b/14.1.2-0-0-SNAPSHOT/docs/main/config.js @@ -725,7 +725,7 @@ function createNav(){ { title: 'Coherence JavaScript Client API', action: 'library_books', - href: 'https://oracle.github.io/coherence/20.06/api/js/index.html', + href: 'https://oracle.github.io/coherence-js-client/', target: '_blank' } ] diff --git a/14.1.2-0-0-SNAPSHOT/docs/main/search-index.json b/14.1.2-0-0-SNAPSHOT/docs/main/search-index.json index ab1eb93e747c5..326e7e1ab9873 100644 --- a/14.1.2-0-0-SNAPSHOT/docs/main/search-index.json +++ b/14.1.2-0-0-SNAPSHOT/docs/main/search-index.json @@ -352,7 +352,7 @@ }, { "location": "/docs/about/01_overview", - "text": " Note The documentation on this site covers new features and improvements that are currently only available in the open source Coherence Community Edition (CE). For complete documentation covering all the features that are available both in the latest commercial editions (Enterprise and Grid Edition) and the Community Edition, please refer to the Official Documentation . Coherence is scalable, fault-tolerant, cloud-ready, distributed platform for building grid-based applications and reliably storing data. The product is used at scale, for both compute and raw storage, in a vast array of industries such as critical financial trading systems, high performance telecommunication products, and eCommerce applications. Typically, these deployments do not tolerate any downtime and Coherence is chosen due its novel features in death detection, application data evolvability, and the robust, battle-hardened core of the product that enables it to be seamlessly deployed and adapted within any ecosystem. At a high level, Coherence provides an implementation of the familiar Map<K,V> interface but rather than storing the associated data in the local process, it is partitioned (or sharded) across a number of designated remote nodes. This partitioning enables applications to not only distribute (and therefore scale) their storage across multiple processes, machines, racks, and data centers, but also to perform grid-based processing to truly harness the CPU resources of the machines. The Coherence interface NamedMap<K,V> (an extension of Map<K,V> provides methods to query, aggregate (map/reduce style), and compute (send functions to storage nodes for locally executed mutations) the data set. These capabilities, in addition to numerous other features, enable Coherence to be used as a framework to write robust, distributed applications. See Core Improvements to learn about new and improved functionality in this release. Please see here for the latest release notes on GitHub. ", + "text": " Note The documentation on this site covers new features and improvements that are currently only available in the open source Coherence Community Edition (CE). For complete documentation covering all the features that are available both in the latest commercial editions (Enterprise and Grid Edition) and the Community Edition, please refer to the Official Documentation . Coherence is scalable, fault-tolerant, cloud-ready, distributed platform for building grid-based applications and reliably storing data. The product is used at scale, for both compute and raw storage, in a vast array of industries such as critical financial trading systems, high performance telecommunication products, and eCommerce applications. Typically, these deployments do not tolerate any downtime and Coherence is chosen due its novel features in death detection, application data evolvability, and the robust, battle-hardened core of the product that enables it to be seamlessly deployed and adapted within any ecosystem. At a high level, Coherence provides an implementation of the familiar Map<K,V> interface but rather than storing the associated data in the local process, it is partitioned (or sharded) across a number of designated remote nodes. This partitioning enables applications to not only distribute (and therefore scale) their storage across multiple processes, machines, racks, and data centers, but also to perform grid-based processing to truly harness the CPU resources of the machines. The Coherence interface NamedMap<K,V> (an extension of Map<K,V> provides methods to query, aggregate (map/reduce style), and compute (send functions to storage nodes for locally executed mutations) the data set. These capabilities, in addition to numerous other features, enable Coherence to be used as a framework to write robust, distributed applications. Please see here for the latest release notes on GitHub. ", "title": "Overview" }, { @@ -1130,16 +1130,6 @@ "text": " Coherence CE 14.1.2.0.0 requires a minimum of version 17 of the Java Development Kit (JDK). Concerning Java Platform Module (JPMS) Options JPMS JDK command line options such as --add-opens , --add-exports and --add-reads of standard JDK modules to com.oracle.coherence module documented in Section Using Java Modules to Build a Coherence Application of Coherence commercial release 14.1.1.2206 are no longer required. A new JPMS requirement is an application module containing Coherence remote lambda(s) must open itself to module com.oracle.coherence so the remote lambda(s) can be resolved to the application’s lambda(s) during deserialization. ", "title": "Java Development Kit Requirements" }, - { - "location": "/docs/about/04_important", - "text": " Coherence CE 14.1.2.0.0 has migrated to Jakarta EE 9.1 from Java EE 8, importing types in jakarta packages instead of javax packages. The following table describes the mapping of javax packages to jakarta packages and Maven artifacts in Coherence CE 14.1.2.0.0. 'javax' Package 'jakarta' Package Maven Group ID Maven Artifact ID Version javax.activation jakarta.activation jakarta.activation jakarta.activation-api 2.0.1 javax.annotation jakarta.annotation jakarta.annotation jakarta.annotation-api 2.0.0 javax.enterprise jakarta.enterprise jakarta.enterprise jakarta.enterprise.cdi-api 3.0.0 javax.inject jakarta.inject jakarta.inject jakarta.inject-api 2.0.1 javax.interceptor jakarta.interceptor jakarta.interceptor jakarta.interceptor-api 2.0.0 javax.jms jakarta.jms jakarta.jms jakarta.jms-api 3.0.0 javax.json jakarta.json jakarta.json jakarta.json-api 2.0.2 javax.json.bind jakarta.json.bind jakarta.json.bind jakarta.json.bind-api 2.0.0 javax.resource jakarta.resource jakarta.resource jakarta.resource-api 2.0.0 javax.ws.rs jakarta.ws.rs jakarta.ws.rs jakarta.ws.rs-api 3.0.0 javax.xml.bind jakarta.xml.bind jakarta.xml.bind jakarta.xml.bind-api 3.0.1 We’ve updated our Coherence CE examples to use the jakarta packages where relevant. These examples still hold for older versions of Coherence CE; in these cases developers will need to change from jakarta to javax . In addition to these standard APIs being migrated, we’ve also updated some of our major dependent libraries that have undertaken this migration as well. Most notably: Library Version Helidon 3.0.0 Jersey 3.0.5 Jackson 2.13.3 Jackson DataBind 2.13.3 Weld 4.0.3.Final JAXB Core 3.0.2 JAXB Implementation 3.0.2 Eclipse MP Config 3.0.1 Eclipse MP Metrics 4.0 Note If using the older jackson-rs-base and jackson-jaxrs-json-provider libraries, it will be necessary to migrate to the 'jakarta' versions. The Maven groupId for the 'jakarta' versions is com.fasterxml.jackson.jakarta.rs with the artifactIds being jackson-jakarta-rs-base and jackson-jakarta-rs-json-provider , respectively. Note If using the older jackson-module-jaxb-annotations library, it will be necessary to migrate to the jakarta versions. The maven groupId for the 'jakarta' version remains the same ( com.fasterxml.jackson.module ), however the artifactId should now be jackson-module-jakarta-xmlbind-annotations ", - "title": "Jakarta EE 9.1 Compatibility" - }, - { - "location": "/docs/about/04_important", - "text": " The following deprecated packages have been removed from this release: com.oracle.datagrid.persistence com.tangosol.persistence com.oracle.common.base (NOTE: these classes are now in com.oracle.coherence.common.base) ", - "title": "Deprecated Code Removal" - }, { "location": "/examples/guides/190-cache-stores/README", "text": " What You Will Build What You Need CacheLoader and CacheStore Interface Simple Cache Store Example Simple CacheLoader Simple CacheStore Enable Write Behind File Cache Store Example HSQLDb Cache Store Example Refresh Ahead Expiring HSQLDb Cache Store Example Write Behind HSQLDb Cache Store Example H2 R2DBC Non Blocking Entry Store Example Pluggable Cache Stores Summary See Also ", diff --git a/14.1.2-0-0-SNAPSHOT/docs/pages/docs/about/01_overview.js b/14.1.2-0-0-SNAPSHOT/docs/pages/docs/about/01_overview.js index 17af711472e73..e3cf98156d30e 100644 --- a/14.1.2-0-0-SNAPSHOT/docs/pages/docs/about/01_overview.js +++ b/14.1.2-0-0-SNAPSHOT/docs/pages/docs/about/01_overview.js @@ -20,9 +20,6 @@ This partitioning enables applications to not only distribute (and therefore sca

The Coherence interface NamedMap<K,V> (an extension of Map<K,V> provides methods to query, aggregate (map/reduce style), and compute (send functions to storage nodes for locally executed mutations) the data set. These capabilities, in addition to numerous other features, enable Coherence to be used as a framework to write robust, distributed applications.

-
-

See Core Improvements to learn about new and improved functionality in this release.

-

Please see here for the latest release notes on GitHub.

diff --git a/14.1.2-0-0-SNAPSHOT/docs/pages/docs/about/04_important.js b/14.1.2-0-0-SNAPSHOT/docs/pages/docs/about/04_important.js index 034a872ce042f..54ce8827ae198 100644 --- a/14.1.2-0-0-SNAPSHOT/docs/pages/docs/about/04_important.js +++ b/14.1.2-0-0-SNAPSHOT/docs/pages/docs/about/04_important.js @@ -14,209 +14,4 @@ - -

Jakarta EE 9.1 Compatibility

-
-

Coherence CE 14.1.2.0.0 has migrated to Jakarta EE 9.1 from Java EE 8, importing types in jakarta packages instead of javax packages. -The following table describes the mapping of javax packages to jakarta packages and Maven artifacts in Coherence CE 14.1.2.0.0.

- - -
- ------- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
'javax' Package'jakarta' PackageMaven Group IDMaven Artifact IDVersion
javax.activationjakarta.activationjakarta.activationjakarta.activation-api2.0.1
javax.annotationjakarta.annotationjakarta.annotationjakarta.annotation-api2.0.0
javax.enterprisejakarta.enterprisejakarta.enterprisejakarta.enterprise.cdi-api3.0.0
javax.injectjakarta.injectjakarta.injectjakarta.inject-api2.0.1
javax.interceptorjakarta.interceptorjakarta.interceptorjakarta.interceptor-api2.0.0
javax.jmsjakarta.jmsjakarta.jmsjakarta.jms-api3.0.0
javax.jsonjakarta.jsonjakarta.jsonjakarta.json-api2.0.2
javax.json.bindjakarta.json.bindjakarta.json.bindjakarta.json.bind-api2.0.0
javax.resourcejakarta.resourcejakarta.resourcejakarta.resource-api2.0.0
javax.ws.rsjakarta.ws.rsjakarta.ws.rsjakarta.ws.rs-api3.0.0
javax.xml.bindjakarta.xml.bindjakarta.xml.bindjakarta.xml.bind-api3.0.1
-
-

We’ve updated our Coherence CE examples to use the jakarta packages where relevant. -These examples still hold for older versions of Coherence CE; in these cases -developers will need to change from jakarta to javax.

- -

In addition to these standard APIs being migrated, we’ve also updated -some of our major dependent libraries that have undertaken this migration as well. -Most notably:

- - -
- ---- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
LibraryVersion
Helidon3.0.0
Jersey3.0.5
Jackson2.13.3
Jackson DataBind2.13.3
Weld4.0.3.Final
JAXB Core3.0.2
JAXB Implementation3.0.2
Eclipse MP Config3.0.1
Eclipse MP Metrics4.0
-
-
-

Note

-

If using the older jackson-rs-base and jackson-jaxrs-json-provider libraries, -it will be necessary to migrate to the 'jakarta' versions. The Maven -groupId for the 'jakarta' versions is com.fasterxml.jackson.jakarta.rs -with the artifactIds being jackson-jakarta-rs-base and jackson-jakarta-rs-json-provider, -respectively.

-

-
-
-

Note

-

If using the older jackson-module-jaxb-annotations library, -it will be necessary to migrate to the jakarta versions. The maven -groupId for the 'jakarta' version remains the same (com.fasterxml.jackson.module), -however the artifactId should now be jackson-module-jakarta-xmlbind-annotations

-

-
-
- -

Deprecated Code Removal

-
-

The following deprecated packages have been removed from this release:

- - -