Doc 36472527 - [35862187->24.09] DOC: update Javadoc for events to clarify that synthetic events work only with distributed caches and their derivatives

Doc 35862187 - DOC: update Javadoc for events to clarify that synthetic events work only with distributed caches and their derivatives
#nobug80
(auto-submit 108144 after successfully running remote remote.full)
Job ID: job.9.20240402142817.10726
(auto-submit integ 108149 main -> coherence-ce/main after successfully running remote remote.full)
Job ID: job.9.20240402155536.19801

[git-p4: depot-paths = "//dev/coherence-ce/main/": change = 108160]

Author: fryp

prj/coherence-core/src/main/java/com/tangosol/net/cache/CacheEvent.java

@@ -1,8 +1,8 @@
 /*
- * Copyright (c) 2000, 2022, Oracle and/or its affiliates.
+ * Copyright (c) 2000, 2024, Oracle and/or its affiliates.
  *
  * Licensed under the Universal Permissive License v 1.0 as shown at
- * http://oss.oracle.com/licenses/upl.
+ * https://oss.oracle.com/licenses/upl.
  */
 
 package com.tangosol.net.cache;
@@ -25,6 +25,13 @@
 * naturally causes either ENTRY_INSERTED or ENTRY_UPDATED event. However, the
 * same event could be as well caused by a client call to a get() method that
 * in turn forces an entry insertion by a cache loader.
+* <p>
+* Not all cache service types support the dispatching of synthetic events.
+* Synthetic events will only be dispatched by a partitioned cache service
+* and its derivatives, such as a federated cache service, or by near, view,
+* or remote caches that are backed by a cache service that supports the
+* dispatching of synthetic events. In all other cases, no event will be dispatched
+* for synthetic events such as expiry.
 *
 * @author gg  2003.09.12
 * @since Coherence 2.3