--- a/corba/src/java.corba/share/classes/org/omg/CosNaming/package.html Wed Jul 05 20:26:30 2017 +0200
+++ b/corba/src/java.corba/share/classes/org/omg/CosNaming/package.html Wed Apr 08 16:01:26 2015 +0400
@@ -3,7 +3,7 @@
<head>
<!--
/*
-* Copyright (c) 1998, 2006, Oracle and/or its affiliates. All rights reserved.
+* Copyright (c) 1998, 2015, Oracle and/or its affiliates. All rights reserved.
* DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
*
* This code is free software; you can redistribute it and/or modify it
@@ -32,20 +32,20 @@
Provides a naming service for Java IDL. The Object Request Broker Daemon
(ORBD) also includes both a transient and persistent naming service.
-
+
<P>
The package and all its classes and interfaces
were generated by running the tool <code>idlj</code> on the file
<code>nameservice.idl</code>, which is a module written in OMG IDL.
-
+
<H3>Package Specification</H3>
-
+
<P>For a precise list of supported sections of official specifications with which
the Java[tm] Platform, Standard Edition 6, ORB complies, see <A
HREF="../CORBA/doc-files/compliance.html">Official Specifications for CORBA
support in Java[tm] SE 6</A>.
- <P>
+
<H2>Interfaces</H2>
The package <tt>org.omg.CosNaming</tt> contains two public interfaces
and several auxiliary classes.
@@ -62,7 +62,7 @@
interface supplies the main functionality for the naming service, and
<code>BindingIterator</code> provides a means of iterating through a list
of name/object reference bindings.
- <P>
+
<H2>Auxiliary Classes</H2>
In order to map an OMG IDL interface to the Java programming language,
the idlj compiler creates Java classes that can be thought of
@@ -70,13 +70,13 @@
Comments for the generated auxiliary classes
used by the interfaces <code>NamingContext</code> and
<code>BindingIterator</code> are included here.
- <P>
+
<H3>Classes Used by <code>NamingContext</code> and
<code>BindingIterator</code></H3>
The following are classes used by
the naming service. (Helper and holder classes, which are
generated for each of the classes listed here, are discussed below.)
-
+
<UL>
<LI><code>public final class <B>NameComponent</B></code> --
a building block for names. (Names are bound to object references
@@ -89,8 +89,7 @@
A <code><B>NameComponent</B></code> object consists of two fields:
<OL>
<LI><code><B>id</B></code> -- a <code>String</code> used as an identifier
- <LI><code><B>kind</B></code> -- a <code>String</code> that can be used for
-any
+ <LI><code><B>kind</B></code> -- a <code>String</code> that can be used for any
descriptive purpose. Its importance is that it
can be used to describe an object without affecting syntax.
The C programming language, for example, uses the the syntactic convention
@@ -102,16 +101,15 @@
<code>"c_source"</code>, <code>"object_code"</code>,
<code>"executable"</code>,
<code>"postscript"</code>, and <code>""</code>. It is not unusual
- for the <code>kind</code> field to be the empty string.
+ for the <code>kind</code> field to be the empty string.
</OL>
<P>
In a name, each <code>NameComponent</code> object except the last denotes
a <code>NamingContext</code> object; the last <code>NameComponent</code>
object denotes the bound object reference.
This is similar to a path name, in which the last name is the
- file name, and all names before it are directory names.<p>
- <P>
-
+ file name, and all names before it are directory names.
+
<LI><code>public final class <B>Binding</B></code> --
an object that associates a name with an object reference or a
naming context.
@@ -125,45 +123,44 @@
</OL>
<P>
The interface <code>NamingContext</code> has methods for
- binding/unbinding names with object references or naming contexts,
- for listing bindings,
+ binding/unbinding names with object references or naming contexts,
+ for listing bindings,
and for resolving bindings (given a name, the method
<code>resolve</code> returns the object reference bound to it).
-
- <P>
- <LI><code>public final class <B>BindingType</B></code> --
+
+ <LI><code>public final class <B>BindingType</B></code> --
an object that specifies whether the given <code>Binding</code>
object is a binding between a name and an object reference (that is,
not a naming context) or between a name and a naming context.
<P>
The class<code>BindingType</code> consists of two methods and
- four constants. Two of these constants are
- <code>BindingType</code> objects, and two are <code>int</code>s.
- <P>
- The <code>BindingType</code> objects
+ four constants. Two of these constants are
+ <code>BindingType</code> objects, and two are <code>int</code>s.
+ <P>
+ The <code>BindingType</code> objects
can be passed to the constructor for the class
<code>Binding</code> or used as parameters or return values. These
- <code>BindingType</code> objects are:
+ <code>BindingType</code> objects are:
<UL>
<LI><code>public static final BindingType <B>nobject</B></code> --
- to indicate that the binding is with an object reference
+ to indicate that the binding is with an object reference
<LI><code>public static final BindingType <B>ncontext</B></code> --
- to indicate that the binding is with a naming context
+ to indicate that the binding is with a naming context
</UL>
<P>
- The <code>int</code> constants can be supplied to the method
- <code>from_int</code> to create <code>BindingType</code> objects,
- or they can be return values for the method <code>value</code>.
- These constants are:
- <UL>
+ The <code>int</code> constants can be supplied to the method
+ <code>from_int</code> to create <code>BindingType</code> objects,
+ or they can be return values for the method <code>value</code>.
+ These constants are:
+ <UL>
<LI><code>public static final int <B>_nobject</B></code>
<LI><code>public static final int <B>_ncontext</B></code>
- </UL>
+ </UL>
If the method <code>from_int</code> is supplied with anything other
- than <code>_nobject</code>
+ than <code>_nobject</code>
or <code>_ncontext</code>, it will throw
- the exception <code>org.omg.CORBA.BAD_PARAM</code>.
- <P>Usage is as follows:
+ the exception <code>org.omg.CORBA.BAD_PARAM</code>.
+ <P>Usage is as follows:
<PRE>
BindingType btObject = from_int(_nobject);
BindingType btContext = from_int(_ncontext);
@@ -182,9 +179,9 @@
int bt = BindingType.value();
</PRE>
</UL>
-
+
<H3>Holder Classes</H3>
-
+
OMG IDL uses OUT and INOUT parameters for returning values from operations.
The mapping to the Java programming language, which does not have OUT
and INOUT parameters, creates a special class for each type, called
@@ -308,7 +305,6 @@
This associates <code>NameService</code> with the Root Naming
Context of the <code>CosNaming</code> implementation that you
want to use.
- <P>
<LI>Start the standalone Bootstrap server using the following command:
<pre>
<code>
@@ -340,13 +336,13 @@
<code>CosNaming</code> API, please see:
<ul>
<li><a href="../../../../technotes/guides/idl/tnameserv.html">
- Naming Service</a>
+ Naming Service</a>
</ul>
<p>
For an overview of Java IDL, please see:
<ul>
<li><a href="../../../../technotes/guides/idl/index.html">
- Java IDL home page</a>
+ Java IDL home page</a>
</ul>
@since JDK1.3