21743
|
1 |
'\" t
|
|
2 |
.\" Copyright (c) 1999, 2013, Oracle and/or its affiliates. All rights reserved.
|
|
3 |
.\"
|
|
4 |
.\" DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
|
|
5 |
.\"
|
|
6 |
.\" This code is free software; you can redistribute it and/or modify it
|
|
7 |
.\" under the terms of the GNU General Public License version 2 only, as
|
|
8 |
.\" published by the Free Software Foundation.
|
|
9 |
.\"
|
|
10 |
.\" This code is distributed in the hope that it will be useful, but WITHOUT
|
|
11 |
.\" ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
|
|
12 |
.\" FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
|
|
13 |
.\" version 2 for more details (a copy is included in the LICENSE file that
|
|
14 |
.\" accompanied this code).
|
|
15 |
.\"
|
|
16 |
.\" You should have received a copy of the GNU General Public License version
|
|
17 |
.\" 2 along with this work; if not, write to the Free Software Foundation,
|
|
18 |
.\" Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
|
|
19 |
.\"
|
|
20 |
.\" Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
|
|
21 |
.\" or visit www.oracle.com if you need additional information or have any
|
|
22 |
.\" questions.
|
|
23 |
.\"
|
|
24 |
.\" Arch: generic
|
|
25 |
.\" Software: JDK 8
|
|
26 |
.\" Date: 21 November 2013
|
|
27 |
.\" SectDesc: Java IDL and RMI-IIOP Tools
|
|
28 |
.\" Title: tnameserv.1
|
|
29 |
.\"
|
|
30 |
.if n .pl 99999
|
|
31 |
.TH tnameserv 1 "21 November 2013" "JDK 8" "Java IDL and RMI-IIOP Tools"
|
|
32 |
.\" -----------------------------------------------------------------
|
|
33 |
.\" * Define some portability stuff
|
|
34 |
.\" -----------------------------------------------------------------
|
|
35 |
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
36 |
.\" http://bugs.debian.org/507673
|
|
37 |
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
|
|
38 |
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
39 |
.ie \n(.g .ds Aq \(aq
|
|
40 |
.el .ds Aq '
|
|
41 |
.\" -----------------------------------------------------------------
|
|
42 |
.\" * set default formatting
|
|
43 |
.\" -----------------------------------------------------------------
|
|
44 |
.\" disable hyphenation
|
|
45 |
.nh
|
|
46 |
.\" disable justification (adjust text to left margin only)
|
|
47 |
.ad l
|
|
48 |
.\" -----------------------------------------------------------------
|
|
49 |
.\" * MAIN CONTENT STARTS HERE *
|
|
50 |
.\" -----------------------------------------------------------------
|
12047
|
51 |
|
21743
|
52 |
.SH NAME
|
|
53 |
tnameserv \- Interface Definition Language (IDL)\&.
|
|
54 |
.SH SYNOPSIS
|
|
55 |
.sp
|
|
56 |
.nf
|
12047
|
57 |
|
21743
|
58 |
\fBtnameserve\fR \fB\-ORBInitialPort\fR [ \fInameserverport\fR ]
|
|
59 |
.fi
|
|
60 |
.sp
|
|
61 |
.TP
|
|
62 |
-ORBInitialPort \fInameserverport\fR
|
|
63 |
.br
|
|
64 |
The initial port where the naming service listens for the bootstrap protocol used to implement the ORB \f3resolve_initial_references\fR and \f3list_initial_references\fR methods\&.
|
|
65 |
.SH DESCRIPTION
|
|
66 |
Java IDL includes the Object Request Broker Daemon (ORBD)\&. ORBD is a daemon process that contains a Bootstrap Service, a Transient Naming Service, a Persistent Naming Service, and a Server Manager\&. The Java IDL tutorials all use ORBD, but you can substitute the \f3tnameserv\fR command for the \f3orbd\fR command in any of the examples that use a Transient Naming Service\&.
|
|
67 |
.PP
|
|
68 |
See orbd(1) or Naming Service at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/jidlNaming\&.html
|
|
69 |
.PP
|
|
70 |
The CORBA Common Object Services (COS) Naming Service provides a tree-structure directory for object references similar to a file system that provides a directory structure for files\&. The Transient Naming Service provided with Java IDL, \f3tnameserv\fR, is a simple implementation of the COS Naming Service specification\&.
|
|
71 |
.PP
|
|
72 |
Object references are stored in the name space by name and each object reference-name pair is called a name binding\&. Name bindings can be organized under naming contexts\&. Naming contexts are name bindings and serve the same organizational function as a file system subdirectory\&. All bindings are stored under the initial naming context\&. The initial naming context is the only persistent binding in the name space\&. The rest of the name space is lost when the Java IDL naming service process stops and restarts\&.
|
|
73 |
.PP
|
|
74 |
For an applet or application to use COS naming, its ORB must know the port of a host running a naming service or have access to an initial naming context string for that naming service\&. The naming service can either be the Java IDL naming service or another COS-compliant naming service\&.
|
|
75 |
.SS START\ THE\ NAMING\ SERVICE
|
|
76 |
You must start the Java IDL naming service before an application or applet that uses its naming service\&. Installation of the Java IDL product creates a script (Oracle Solaris: \f3tnameserv\fR) or executable file (Windows: \f3tnameserv\&.exe\fR) that starts the Java IDL naming service\&. Start the naming service so it runs in the background\&.
|
|
77 |
.PP
|
|
78 |
If you do not specify otherwise, then the Java IDL naming service listens on port 900 for the bootstrap protocol used to implement the ORB \f3resolve_initial_references\fR and \f3list_initial_references methods\fR, as follows:
|
|
79 |
.sp
|
|
80 |
.nf
|
|
81 |
\f3tnameserv \-ORBInitialPort nameserverport&\fP
|
|
82 |
.fi
|
|
83 |
.nf
|
|
84 |
\f3\fP
|
|
85 |
.fi
|
|
86 |
.sp
|
|
87 |
If you do not specify the name server port, then port 900 is used by default\&. When running Oracle Solaris software, you must become the root user to start a process on a port below 1024\&. For this reason, it is recommended that you use a port number greater than or equal to 1024\&. To specify a different port, for example, 1050, and to run the naming service in the background, from a UNIX command shell, enter:
|
|
88 |
.sp
|
|
89 |
.nf
|
|
90 |
\f3tnameserv \-ORBInitialPort 1050&\fP
|
|
91 |
.fi
|
|
92 |
.nf
|
|
93 |
\f3\fP
|
|
94 |
.fi
|
|
95 |
.sp
|
|
96 |
From an MS-DOS system prompt (Windows), enter:
|
|
97 |
.sp
|
|
98 |
.nf
|
|
99 |
\f3start tnameserv \-ORBInitialPort 1050\fP
|
|
100 |
.fi
|
|
101 |
.nf
|
|
102 |
\f3\fP
|
|
103 |
.fi
|
|
104 |
.sp
|
|
105 |
Clients of the name server must be made aware of the new port number\&. Do this by setting the \f3org\&.omg\&.CORBA\&.ORBInitialPort\fR property to the new port number when you create the ORB object\&.
|
|
106 |
.SS RUN\ THE\ SERVER\ AND\ CLIENT\ ON\ DIFFERENT\ HOSTS
|
|
107 |
In most of the Java IDL and RMI-IIOP tutorials, the naming service, server, and client are all running on the development machine\&. In real-world deployment, the client and server probably run on different host machines from the Naming Service\&.
|
|
108 |
.PP
|
|
109 |
For the client and server to find the Naming Service, they must be made aware of the port number and host on which the naming service is running\&. Do this by setting the \f3org\&.omg\&.CORBA\&.ORBInitialPort\fR and \f3org\&.omg\&.CORBA\&.ORBInitialHost\fR properties in the client and server files to the machine name and port number on which the Naming Service is running\&. An example of this is shown in Getting Started Using RMI-IIOP at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/rmi-iiop/rmiiiopexample\&.html
|
|
110 |
.PP
|
|
111 |
You could also use the command-line options \f3-ORBInitialPort nameserverport#\fR and \f3-ORBInitialHost nameserverhostname\fR to tell the client and server where to find the naming service\&. For one example of doing this using the command-line option, see Java IDL: The Hello World Example on Two Machines at http://docs\&.oracle\&.com/javase/8/docs/technotes/guides/idl/tutorial/jidl2machines\&.html
|
|
112 |
.PP
|
|
113 |
For example, suppose the Transient Naming Service, \f3tnameserv\fR is running on port 1050 on host \f3nameserverhost\fR\&. The client is running on host \f3clienthost,\fR and the server is running on host \f3serverhost\fR\&.
|
|
114 |
.PP
|
|
115 |
Start \f3tnameserv\fR on the host \f3nameserverhost\fR:
|
|
116 |
.sp
|
|
117 |
.nf
|
|
118 |
\f3tnameserv \-ORBInitialPort 1050\fP
|
|
119 |
.fi
|
|
120 |
.nf
|
|
121 |
\f3\fP
|
|
122 |
.fi
|
|
123 |
.sp
|
|
124 |
Start the server on the \f3serverhost\fR:
|
|
125 |
.sp
|
|
126 |
.nf
|
|
127 |
\f3java Server \-ORBInitialPort 1050 \-ORBInitialHost nameserverhost\fP
|
|
128 |
.fi
|
|
129 |
.nf
|
|
130 |
\f3\fP
|
|
131 |
.fi
|
|
132 |
.sp
|
|
133 |
Start the client on the \f3clienthost\fR:
|
|
134 |
.sp
|
|
135 |
.nf
|
|
136 |
\f3java Client \-ORBInitialPort 1050 \-ORBInitialHost nameserverhost\fP
|
|
137 |
.fi
|
|
138 |
.nf
|
|
139 |
\f3\fP
|
|
140 |
.fi
|
|
141 |
.sp
|
|
142 |
.SS STOP\ THE\ NAMING\ SERVICE
|
|
143 |
To stop the Java IDL naming service, use the relevant operating system command, such as \f3kill\fR for a Unix process or \f3Ctrl+C\fR for a Windows process\&. The naming service continues to wait for invocations until it is explicitly shut down\&. Note that names registered with the Java IDL naming service disappear when the service is terminated\&.
|
|
144 |
.SH OPTIONS
|
|
145 |
.TP
|
|
146 |
-J\fIoption\fR
|
|
147 |
.br
|
|
148 |
Passes \f3option\fR to the Java Virtual Machine, where \f3option\fR is one of the options described on the reference page for the Java application launcher\&. For example, \f3-J-Xms48m\fR sets the startup memory to 48 MB\&. See java(1)\&.
|
|
149 |
.SH EXAMPLES
|
|
150 |
.SS ADD\ OBJECTS\ TO\ THE\ NAME\ SPACE
|
|
151 |
The following example shows how to add names to the name space\&. It is a self-contained Transient Naming Service client that creates the following simple tree\&.
|
|
152 |
.sp
|
|
153 |
.nf
|
|
154 |
\f3Initial Naming Context\fP
|
|
155 |
.fi
|
|
156 |
.nf
|
|
157 |
\f3 plans\fP
|
|
158 |
.fi
|
|
159 |
.nf
|
|
160 |
\f3 Personal\fP
|
|
161 |
.fi
|
|
162 |
.nf
|
|
163 |
\f3 calendar\fP
|
|
164 |
.fi
|
|
165 |
.nf
|
|
166 |
\f3 schedule\fP
|
|
167 |
.fi
|
|
168 |
.nf
|
|
169 |
\f3\fP
|
|
170 |
.fi
|
|
171 |
.sp
|
|
172 |
In this example, \f3plans\fR is an object reference and \f3Personal\fR is a naming context that contains two object references: \f3calendar\fR and \f3schedule\fR\&.
|
|
173 |
.sp
|
|
174 |
.nf
|
|
175 |
\f3import java\&.util\&.Properties;\fP
|
|
176 |
.fi
|
|
177 |
.nf
|
|
178 |
\f3import org\&.omg\&.CORBA\&.*;\fP
|
|
179 |
.fi
|
|
180 |
.nf
|
|
181 |
\f3import org\&.omg\&.CosNaming\&.*;\fP
|
|
182 |
.fi
|
|
183 |
.nf
|
|
184 |
\f3\fP
|
|
185 |
.fi
|
|
186 |
.nf
|
|
187 |
\f3public class NameClient {\fP
|
|
188 |
.fi
|
|
189 |
.nf
|
|
190 |
\f3\fP
|
|
191 |
.fi
|
|
192 |
.nf
|
|
193 |
\f3 public static void main(String args[]) {\fP
|
|
194 |
.fi
|
|
195 |
.nf
|
|
196 |
\f3\fP
|
|
197 |
.fi
|
|
198 |
.nf
|
|
199 |
\f3 try {\fP
|
|
200 |
.fi
|
|
201 |
.nf
|
|
202 |
\f3\fP
|
|
203 |
.fi
|
|
204 |
.sp
|
|
205 |
In Start the Naming Service, the \f3nameserver\fR was started on port 1050\&. The following code ensures that the client program is aware of this port number\&.
|
|
206 |
.sp
|
|
207 |
.nf
|
|
208 |
\f3 Properties props = new Properties();\fP
|
|
209 |
.fi
|
|
210 |
.nf
|
|
211 |
\f3 props\&.put("org\&.omg\&.CORBA\&.ORBInitialPort", "1050");\fP
|
|
212 |
.fi
|
|
213 |
.nf
|
|
214 |
\f3 ORB orb = ORB\&.init(args, props);\fP
|
|
215 |
.fi
|
|
216 |
.nf
|
|
217 |
\f3\fP
|
|
218 |
.fi
|
|
219 |
.sp
|
|
220 |
This code obtains the initial naming context and assigns it to \f3ctx\fR\&. The second line copies \f3ctx\fR into a dummy object reference \f3objref\fR that is attached to various names and added into the name space\&.
|
|
221 |
.sp
|
|
222 |
.nf
|
|
223 |
\f3 NamingContext ctx =\fP
|
|
224 |
.fi
|
|
225 |
.nf
|
|
226 |
\f3 NamingContextHelper\&.narrow(\fP
|
|
227 |
.fi
|
|
228 |
.nf
|
|
229 |
\f3 orb\&.resolve_initial_references("NameService"));\fP
|
|
230 |
.fi
|
|
231 |
.nf
|
|
232 |
\f3 NamingContext objref = ctx;\fP
|
|
233 |
.fi
|
|
234 |
.nf
|
|
235 |
\f3\fP
|
|
236 |
.fi
|
|
237 |
.sp
|
|
238 |
This code creates a name \f3plans\fR of type \f3text\fR and binds it to the dummy object reference\&. \f3plans\fR is then added under the initial naming context using the \f3rebind\fR method\&. The \f3rebind\fR method enables you to run this program over and over again without getting the exceptions from using the \f3bind\fR method\&.
|
|
239 |
.sp
|
|
240 |
.nf
|
|
241 |
\f3 NameComponent nc1 = new NameComponent("plans", "text");\fP
|
|
242 |
.fi
|
|
243 |
.nf
|
|
244 |
\f3 NameComponent[] name1 = {nc1};\fP
|
|
245 |
.fi
|
|
246 |
.nf
|
|
247 |
\f3 ctx\&.rebind(name1, objref);\fP
|
|
248 |
.fi
|
|
249 |
.nf
|
|
250 |
\f3 System\&.out\&.println("plans rebind successful!");\fP
|
|
251 |
.fi
|
|
252 |
.nf
|
|
253 |
\f3\fP
|
|
254 |
.fi
|
|
255 |
.sp
|
|
256 |
This code creates a naming context called \f3Personal\fR of type \f3directory\fR\&. The resulting object reference, \f3ctx2\fR, is bound to the \f3name\fR and added under the initial naming context\&.
|
|
257 |
.sp
|
|
258 |
.nf
|
|
259 |
\f3 NameComponent nc2 = new NameComponent("Personal", "directory");\fP
|
|
260 |
.fi
|
|
261 |
.nf
|
|
262 |
\f3 NameComponent[] name2 = {nc2};\fP
|
|
263 |
.fi
|
|
264 |
.nf
|
|
265 |
\f3 NamingContext ctx2 = ctx\&.bind_new_context(name2);\fP
|
|
266 |
.fi
|
|
267 |
.nf
|
|
268 |
\f3 System\&.out\&.println("new naming context added\&.\&.");\fP
|
|
269 |
.fi
|
|
270 |
.nf
|
|
271 |
\f3\fP
|
|
272 |
.fi
|
|
273 |
.sp
|
|
274 |
The remainder of the code binds the dummy object reference using the names \f3schedule\fR and \f3calendar\fR under the \f3Personal\fR naming context (\f3ctx2\fR)\&.
|
|
275 |
.sp
|
|
276 |
.nf
|
|
277 |
\f3 NameComponent nc3 = new NameComponent("schedule", "text");\fP
|
|
278 |
.fi
|
|
279 |
.nf
|
|
280 |
\f3 NameComponent[] name3 = {nc3};\fP
|
|
281 |
.fi
|
|
282 |
.nf
|
|
283 |
\f3 ctx2\&.rebind(name3, objref);\fP
|
|
284 |
.fi
|
|
285 |
.nf
|
|
286 |
\f3 System\&.out\&.println("schedule rebind successful!");\fP
|
|
287 |
.fi
|
|
288 |
.nf
|
|
289 |
\f3\fP
|
|
290 |
.fi
|
|
291 |
.nf
|
|
292 |
\f3 NameComponent nc4 = new NameComponent("calender", "text");\fP
|
|
293 |
.fi
|
|
294 |
.nf
|
|
295 |
\f3 NameComponent[] name4 = {nc4};\fP
|
|
296 |
.fi
|
|
297 |
.nf
|
|
298 |
\f3 ctx2\&.rebind(name4, objref);\fP
|
|
299 |
.fi
|
|
300 |
.nf
|
|
301 |
\f3 System\&.out\&.println("calender rebind successful!");\fP
|
|
302 |
.fi
|
|
303 |
.nf
|
|
304 |
\f3 } catch (Exception e) {\fP
|
|
305 |
.fi
|
|
306 |
.nf
|
|
307 |
\f3 e\&.printStackTrace(System\&.err);\fP
|
|
308 |
.fi
|
|
309 |
.nf
|
|
310 |
\f3 }\fP
|
|
311 |
.fi
|
|
312 |
.nf
|
|
313 |
\f3 }\fP
|
|
314 |
.fi
|
|
315 |
.nf
|
|
316 |
\f3}\fP
|
|
317 |
.fi
|
|
318 |
.nf
|
|
319 |
\f3\fP
|
|
320 |
.fi
|
|
321 |
.sp
|
|
322 |
.SS BROWSING\ THE\ NAME\ SPACE
|
|
323 |
The following sample program shoes how to browse the name space\&.
|
|
324 |
.sp
|
|
325 |
.nf
|
|
326 |
\f3import java\&.util\&.Properties;\fP
|
|
327 |
.fi
|
|
328 |
.nf
|
|
329 |
\f3import org\&.omg\&.CORBA\&.*;\fP
|
|
330 |
.fi
|
|
331 |
.nf
|
|
332 |
\f3import org\&.omg\&.CosNaming\&.*;\fP
|
|
333 |
.fi
|
|
334 |
.nf
|
|
335 |
\f3\fP
|
|
336 |
.fi
|
|
337 |
.nf
|
|
338 |
\f3public class NameClientList {\fP
|
|
339 |
.fi
|
|
340 |
.nf
|
|
341 |
\f3\fP
|
|
342 |
.fi
|
|
343 |
.nf
|
|
344 |
\f3 public static void main(String args[]) {\fP
|
|
345 |
.fi
|
|
346 |
.nf
|
|
347 |
\f3\fP
|
|
348 |
.fi
|
|
349 |
.nf
|
|
350 |
\f3 try {\fP
|
|
351 |
.fi
|
|
352 |
.nf
|
|
353 |
\f3\fP
|
|
354 |
.fi
|
|
355 |
.sp
|
|
356 |
In Start the Naming Service, the \f3nameserver\fR was started on port 1050\&. The following code ensures that the client program is aware of this port number\&.
|
|
357 |
.sp
|
|
358 |
.nf
|
|
359 |
\f3 Properties props = new Properties();\fP
|
|
360 |
.fi
|
|
361 |
.nf
|
|
362 |
\f3 props\&.put("org\&.omg\&.CORBA\&.ORBInitialPort", "1050");\fP
|
|
363 |
.fi
|
|
364 |
.nf
|
|
365 |
\f3 ORB orb = ORB\&.init(args, props);\fP
|
|
366 |
.fi
|
|
367 |
.nf
|
|
368 |
\f3\fP
|
|
369 |
.fi
|
|
370 |
.sp
|
|
371 |
The following code obtains the initial naming context\&.
|
|
372 |
.sp
|
|
373 |
.nf
|
|
374 |
\f3 NamingContext nc =\fP
|
|
375 |
.fi
|
|
376 |
.nf
|
|
377 |
\f3 NamingContextHelper\&.narrow(\fP
|
|
378 |
.fi
|
|
379 |
.nf
|
|
380 |
\f3 orb\&.resolve_initial_references("NameService"));\fP
|
|
381 |
.fi
|
|
382 |
.nf
|
|
383 |
\f3\fP
|
|
384 |
.fi
|
|
385 |
.sp
|
|
386 |
The \f3list\fR method lists the bindings in the naming context\&. In this case, up to 1000 bindings from the initial naming context will be returned in the \f3BindingListHolder\fR; any remaining bindings are returned in the \f3BindingIteratorHolder\fR\&.
|
|
387 |
.sp
|
|
388 |
.nf
|
|
389 |
\f3 BindingListHolder bl = new BindingListHolder();\fP
|
|
390 |
.fi
|
|
391 |
.nf
|
|
392 |
\f3 BindingIteratorHolder blIt= new BindingIteratorHolder();\fP
|
|
393 |
.fi
|
|
394 |
.nf
|
|
395 |
\f3 nc\&.list(1000, bl, blIt);\fP
|
|
396 |
.fi
|
|
397 |
.nf
|
|
398 |
\f3\fP
|
|
399 |
.fi
|
|
400 |
.sp
|
|
401 |
This code gets the array of bindings out of the returned \f3BindingListHolder\fR\&. If there are no bindings, then the program ends\&.
|
|
402 |
.sp
|
|
403 |
.nf
|
|
404 |
\f3 Binding bindings[] = bl\&.value;\fP
|
|
405 |
.fi
|
|
406 |
.nf
|
|
407 |
\f3 if (bindings\&.length == 0) return;\fP
|
|
408 |
.fi
|
|
409 |
.nf
|
|
410 |
\f3\fP
|
|
411 |
.fi
|
|
412 |
.sp
|
|
413 |
The remainder of the code loops through the bindings and prints outs the names\&.
|
|
414 |
.sp
|
|
415 |
.nf
|
|
416 |
\f3 for (int i=0; i < bindings\&.length; i++) {\fP
|
|
417 |
.fi
|
|
418 |
.nf
|
|
419 |
\f3\fP
|
|
420 |
.fi
|
|
421 |
.nf
|
|
422 |
\f3 // get the object reference for each binding\fP
|
|
423 |
.fi
|
|
424 |
.nf
|
|
425 |
\f3 org\&.omg\&.CORBA\&.Object obj = nc\&.resolve(bindings[i]\&.binding_name);\fP
|
|
426 |
.fi
|
|
427 |
.nf
|
|
428 |
\f3 String objStr = orb\&.object_to_string(obj);\fP
|
|
429 |
.fi
|
|
430 |
.nf
|
|
431 |
\f3 int lastIx = bindings[i]\&.binding_name\&.length\-1;\fP
|
|
432 |
.fi
|
|
433 |
.nf
|
|
434 |
\f3\fP
|
|
435 |
.fi
|
|
436 |
.nf
|
|
437 |
\f3 // check to see if this is a naming context\fP
|
|
438 |
.fi
|
|
439 |
.nf
|
|
440 |
\f3 if (bindings[i]\&.binding_type == BindingType\&.ncontext) {\fP
|
|
441 |
.fi
|
|
442 |
.nf
|
|
443 |
\f3 System\&.out\&.println("Context: " +\fP
|
|
444 |
.fi
|
|
445 |
.nf
|
|
446 |
\f3 bindings[i]\&.binding_name[lastIx]\&.id);\fP
|
|
447 |
.fi
|
|
448 |
.nf
|
|
449 |
\f3 } else {\fP
|
|
450 |
.fi
|
|
451 |
.nf
|
|
452 |
\f3 System\&.out\&.println("Object: " +\fP
|
|
453 |
.fi
|
|
454 |
.nf
|
|
455 |
\f3 bindings[i]\&.binding_name[lastIx]\&.id);\fP
|
|
456 |
.fi
|
|
457 |
.nf
|
|
458 |
\f3 }\fP
|
|
459 |
.fi
|
|
460 |
.nf
|
|
461 |
\f3 }\fP
|
|
462 |
.fi
|
|
463 |
.nf
|
|
464 |
\f3 } catch (Exception e) {\fP
|
|
465 |
.fi
|
|
466 |
.nf
|
|
467 |
\f3 e\&.printStackTrace(System\&.err)\fP
|
|
468 |
.fi
|
|
469 |
.nf
|
|
470 |
\f3 }\fP
|
|
471 |
.fi
|
|
472 |
.nf
|
|
473 |
\f3 }\fP
|
|
474 |
.fi
|
|
475 |
.nf
|
|
476 |
\f3}\fP
|
|
477 |
.fi
|
|
478 |
.nf
|
|
479 |
\f3\fP
|
|
480 |
.fi
|
|
481 |
.sp
|
|
482 |
.SH SEE\ ALSO
|
|
483 |
.TP 0.2i
|
|
484 |
\(bu
|
|
485 |
orbd(1)
|
|
486 |
.RE
|
|
487 |
.br
|
|
488 |
'pl 8.5i
|
|
489 |
'bp
|