From 1d80392b91fca57d7cd3fd8e2dc7dd214735276b Mon Sep 17 00:00:00 2001 From: nmorozov Date: Thu, 21 Sep 2006 14:14:10 +0400 Subject: [PATCH] yet one more classlib doc added --- xdocs/subcomponents/classlibrary/RMIprovider.htm | 260 ++++++++++++++++++++ xdocs/subcomponents/classlibrary/rmi_proivider.xml | 30 ++ 2 files changed, 290 insertions(+), 0 deletions(-) diff --git a/xdocs/subcomponents/classlibrary/RMIprovider.htm b/xdocs/subcomponents/classlibrary/RMIprovider.htm new file mode 100755 index 0000000..ffc5e48 --- /dev/null +++ b/xdocs/subcomponents/classlibrary/RMIprovider.htm @@ -0,0 +1,260 @@ + + + + + + DRL RMI Registry Service Provider for JNDI + + + + + +

DRL RMI Registry Service Provider for JNDI

+

+ Revision History +

+

+ Disclaimer and Legal Information +

+

+ About This Document +

+

+ Purpose +

+

+ Intended Audience +

+

+ Documentation Conventions +

+

+ RMI Provider Overview +

+

+ RMI Provider in DRL +

+

+ About +

+

+ Environment Properties +

+

+ RMI URLs +

+

+ Binding Registry Contexts and Remote Objects +

+

+ References +

+

+ Revision History +

+ + + + + + + + + + + + + + + + +
+ Version + + Version Information + + Date +
+ Initial version + + Vasily Zakharov, Nadya Morozova: document created. + + March 23, 2006 +
+ Formatting update + + Nadya Morozova: document created. + + September 21, 2006 +
+

+ Disclaimer and Legal Information +

+

+ Copyright 2005-2006 The Apache Software Foundation or its licensors, as + applicable. +

+

+ Licensed under the Apache License, Version 2.0 (the License); you may + not use this file except in compliance with the License. You may + obtain a copy of the License at + http://www.apache.org/licenses/LICENSE-2.0.

+

+ Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied. See the License for the specific language governing + permissions and limitations under the License. +

+

+ About This Document +

+

+ Purpose +

+ +

This document describes the functionality of the DRL RMI [2] Registry Service + Provider for JNDI [1]. The document gives details on the provider design.

+

+ Intended Audience +

+ +

The target audience for the document includes a wide community of engineers + interested in using the RMI registry in their JNDI applications and in further + work with the product to contribute to its development. The document assumes + that readers are familiar with RMI, JNDI and the Java programming language. +

+

+ Documentation Conventions +

+ +

This document uses the unified conventions for the DRL documentation kit.

+

+ Back to Top +

+

+ RMI Provider Overview +

+ +

The RMI registry context, based on a registry location, and the RMI Registry + Service Provider allow JNDI applications to access remote objects bound in the + RMI registry, as described in the Java* RMI Specification [2].

+

+ The provider supplies JNDI with the same essential functionality as + the java.rmi.Naming class does. +

+

+ Back to Top +

+ +

RMI Provider in DRL

+

+ About +

+ +

The DRL RMI Service Provider is an independent implementation of the RMI Service Provider for JNDI. +You can also consult additional information resources on RMI [2], RMI Service Provider [3] and JNDI in general [1].

+ +

The provider can store java.rmi.Remote, javax.naming.Reference + and javax.naming.Referenceable objects. The RMI registry context + and references to individual RMI objects can be bound into other JNDI contexts. + The DRL provider does not support binding other contexts into the RMI registry, + so that you cannot address objects in this context using composite name requests + through the registry.

+

+ Back to Top +

+

+ Environment Properties +

+ +

In addition to the general properties [3], the DRL RMI Registry + Provider uses the following JNDI environment properties:

+
+
+ + java.naming.factory.initial +
+
+

+ Specifies the RMI registry service provider class name as the + initial context factory to be used by the + javax.naming.InitialContext class.

+

+ Example +

+
+  env.put(Context.INITIAL_CONTEXT_FACTORY,
+        "org.apache.harmony.jndi.provider.rmi.registry.RegistryContextFactory");
+

+ Use this property with the java.naming.provider.url + property, which specifies the location of the RMI registry + for the usage of the initial context. Otherwise, the initial + context you created can only resolve complete RMI URLs. +

+
+
+
+ +
org.apache.harmony.jndi.provider.rmi.registry.clientSocketFactory +
+ +
Can contain the name of a class implementing the java.rmi.server.RMIClientSocketFactory + interface. The instance of this class is passed to the java.rmi.registry.LocateRegistry.getRegistry() + method.
+
+

+ Back to Top +

+

+ RMI URLs +

+ +

The URL context factory, org.apache.harmony.jndi.provider.rmi.rmiURLContextFactory, + enables passing RMI URLs as names to the JNDI initial context.

+

+ Back to Top +

+

+ Binding Registry Contexts and Remote Objects +

+ +

The class org.apache.harmony.jndi.provider.rmi.registry.RegistryContextFactory + implements the javax.naming.spi.ObjectFactory interface + and provides converting registry references into the corresponding registry + contexts or remote objects.

+

+ Back to Top +

+

+ References +

+

+ [1] Sun about JNDI, http://java.sun.com/j2se/1.5.0/docs/guide/jndi/ +

+

+ [2] RMI Specification, http://java.sun.com/j2se/1.5.0/docs/guide/rmi/spec/rmiTOC.html +

+

+ [3] Sun's RMI Provider, http://java.sun.com/j2se/1.5.0/docs/guide/jndi/jndi-rmi.html +

+

+ Back to Top +

+

+ * Other brands and names are the property of their + respective owners. +

+ + + + diff --git a/xdocs/subcomponents/classlibrary/rmi_proivider.xml b/xdocs/subcomponents/classlibrary/rmi_proivider.xml new file mode 100755 index 0000000..f4e2d2f --- /dev/null +++ b/xdocs/subcomponents/classlibrary/rmi_proivider.xml @@ -0,0 +1,30 @@ + + + + + + + + Apache Harmony + Harmony Documentation Team + + + + + + -- 1.4.1