You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jackrabbit.apache.org by re...@apache.org on 2019/04/29 13:21:02 UTC
svn commit: r1858370 - in
/jackrabbit/trunk/jackrabbit-jcr-rmi/src/main/javadoc/org/apache/jackrabbit/rmi:
observation/package.html remote/package.html
Author: reschke
Date: Mon Apr 29 13:21:02 2019
New Revision: 1858370
URL: http://svn.apache.org/viewvc?rev=1858370&view=rev
Log:
JCR-4430: fix javadoc:javadoc for jdk >= 11 - unescaped '<'
Modified:
jackrabbit/trunk/jackrabbit-jcr-rmi/src/main/javadoc/org/apache/jackrabbit/rmi/observation/package.html
jackrabbit/trunk/jackrabbit-jcr-rmi/src/main/javadoc/org/apache/jackrabbit/rmi/remote/package.html
Modified: jackrabbit/trunk/jackrabbit-jcr-rmi/src/main/javadoc/org/apache/jackrabbit/rmi/observation/package.html
URL: http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-jcr-rmi/src/main/javadoc/org/apache/jackrabbit/rmi/observation/package.html?rev=1858370&r1=1858369&r2=1858370&view=diff
==============================================================================
--- jackrabbit/trunk/jackrabbit-jcr-rmi/src/main/javadoc/org/apache/jackrabbit/rmi/observation/package.html (original)
+++ jackrabbit/trunk/jackrabbit-jcr-rmi/src/main/javadoc/org/apache/jackrabbit/rmi/observation/package.html Mon Apr 29 13:21:02 2019
@@ -15,26 +15,20 @@
limitations under the License.
-->
<body>
-
<p>
Helper class used by the observation manager classes.
-</p>
-
-<p>
The JCR observation framework defines a notification mechanism where an
<code>EventListener</code> is registered with the observation manager
to receive certain events during the lifetime of the registration. For
the remote case, where the repository and the application run in different
Java VMs on possibly different hosts, there are issues related to the
observation framework.
-
<p>
The listener mechanism is a call-back mechanism where the server calls
code in the client application. The client application code most probably
hooks into other parts of that application. Therefore it is not practically
feasible to just require the client listener to be serializable to be sent
to the server for several reasons:
-
<ul>
<li>The RMI server cannot call any method on the RMI client. To support such
call-back situations, the client side application would have to register
@@ -42,14 +36,12 @@ another server, which the server side wo
<li>When trying to "transfer" the listener to the server side, the listener
class would have to be available to the server side - either locally in the
class path or through RMI class loading mechanisms.
-<ul>
-
+</ul>
<p>
To circumvent these issues and still be able to register event listeners,
support for observation events is implemented in a manner similar to the Java
Management Extensions Remote API 1.0 (JSR 160) as laid out in Chapter 2.4,
Adding Remote Listeners:
-
<p>
The ObservationManager interface is not implemented in the RMI layer like
other interfaces, which just forward calls to the API to the corresponding
@@ -57,7 +49,6 @@ remote object by means of the RMI framew
ObservationManager manages its own list of registered event listeners. Each
listener registered with an ObservationManager is assigned a unique
identifier.
-
<p>
The unique identifier along with the filter configuration (event type,
path, depth flag, uuid list, node type list, local flag) is sent to the
@@ -66,18 +57,15 @@ event listener representing the client s
unique identifier as a ilnk to the client side event listener. The proxy
event listener is the registered to the repository's ObservationManager
with the configuration received from the client side.
-
<p>
When an event arrives at the event listener proxy, the proxy creates a
new RemoteEvent instance, which contains the client-side event listener
identifier along with the Event objects from the EventIterator. This
RemoteEvent instance is added to a server-side queue, which may be
retrieved from the client-side.
-
<p>
The client-side ObservationManager has a helper class ClientEventPoll,
which works in the background asking the server for the RemoteEvents from
the event queue. Each such event is then dispatched to the client-side
event listener by calling the EventListener.onEvent() method.
-
</body>
Modified: jackrabbit/trunk/jackrabbit-jcr-rmi/src/main/javadoc/org/apache/jackrabbit/rmi/remote/package.html
URL: http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-jcr-rmi/src/main/javadoc/org/apache/jackrabbit/rmi/remote/package.html?rev=1858370&r1=1858369&r2=1858370&view=diff
==============================================================================
--- jackrabbit/trunk/jackrabbit-jcr-rmi/src/main/javadoc/org/apache/jackrabbit/rmi/remote/package.html (original)
+++ jackrabbit/trunk/jackrabbit-jcr-rmi/src/main/javadoc/org/apache/jackrabbit/rmi/remote/package.html Mon Apr 29 13:21:02 2019
@@ -22,7 +22,7 @@ the client and server sides of the trans
The compiled contents of this package should thus be included
in both client and server installations. Note also that RMI stubs and
skeletons need to be generated for all the remote interfaces when using
-old JDK versions (stubs for JDK < 1.5, skeletons for JDK < 1.2).
+old JDK versions (stubs for JDK < 1.5, skeletons for JDK < 1.2).
<p>
The interfaces in this package are remote versions of the
corresponding interfaces in the javax.jcr packages. They are used by