equal
deleted
inserted
replaced
1 .'" t |
1 ." Copyright 2001-2006 Sun Microsystems, Inc. All Rights Reserved. |
2 ." Copyright 2006 Sun Microsystems, Inc. All Rights Reserved. |
|
3 ." DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER. |
2 ." DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER. |
4 ." |
3 ." |
5 ." This code is free software; you can redistribute it and/or modify it |
4 ." This code is free software; you can redistribute it and/or modify it |
6 ." under the terms of the GNU General Public License version 2 only, as |
5 ." under the terms of the GNU General Public License version 2 only, as |
7 ." published by the Free Software Foundation. |
6 ." published by the Free Software Foundation. |
17 ." Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. |
16 ." Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. |
18 ." |
17 ." |
19 ." Please contact Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, |
18 ." Please contact Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, |
20 ." CA 95054 USA or visit www.sun.com if you need additional information or |
19 ." CA 95054 USA or visit www.sun.com if you need additional information or |
21 ." have any questions. |
20 ." have any questions. |
22 ." ` |
21 ." |
23 .TH idlj 1 "07 Aug 2006" |
22 .TH idlj 1 "04 May 2009" |
24 ." Generated by html2man |
23 ." Generated from HTML by html2man (author: Eric Armstrong) |
25 |
24 |
26 .LP |
25 .LP |
27 .SH NAME |
26 .SH "Name" |
28 idlj \- The IDL\-to\-Java Compiler |
27 idlj \- The IDL\-to\-Java Compiler |
29 .LP |
28 .LP |
30 .RS 3 |
29 .RS 3 |
31 |
30 |
32 .LP |
31 .LP |
50 .LP |
49 .LP |
51 .SH "Description" |
50 .SH "Description" |
52 .LP |
51 .LP |
53 |
52 |
54 .LP |
53 .LP |
55 The IDL\-to\-Java Compiler generates the Java bindings for a given IDL file.\ For binding details, see the OMG IDL to Java Language Language Mapping Specification. Some previous releases of the IDL\-to\-Java compiler were named \f2idltojava\fP. |
54 The IDL\-to\-Java Compiler generates the Java bindings for a given IDL file.\ For binding details, see the |
|
55 .na |
|
56 \f2OMG IDL to Java Language Language Mapping Specification\fP @ |
|
57 .fi |
|
58 http://java.sun.com/javase/6/docs/technotes/guides/idl/mapping/jidlMapping.html. Some previous releases of the IDL\-to\-Java compiler were named \f2idltojava\fP. |
56 .SS |
59 .SS |
57 Emitting Client and Server Bindings |
60 Emitting Client and Server Bindings |
58 .LP |
61 .LP |
59 .RS 3 |
62 .RS 3 |
60 |
63 |
74 .LP |
77 .LP |
75 .LP |
78 .LP |
76 The default server\-side model is the \f2Portable Servant Inheritance Model\fP. Given an interface \f2My\fP defined in \f2My.idl\fP, the file \f2MyPOA.java\fP is generated. You must provide the implementation for \f2My\fP and it must inherit from \f2MyPOA\fP. |
79 The default server\-side model is the \f2Portable Servant Inheritance Model\fP. Given an interface \f2My\fP defined in \f2My.idl\fP, the file \f2MyPOA.java\fP is generated. You must provide the implementation for \f2My\fP and it must inherit from \f2MyPOA\fP. |
77 .LP |
80 .LP |
78 .LP |
81 .LP |
79 \f2MyPOA.java\fP is a stream\-based skeleton that extends \f2org.omg.PortableServer.Servant\fP and implements the \f2InvokeHandler\fP interface and the operations interface associated with the IDL interface the skeleton implements. |
82 \f2MyPOA.java\fP is a stream\-based skeleton that extends |
80 .LP |
83 .na |
81 .LP |
84 \f2org.omg.PortableServer.Servant\fP @ |
82 The \f2PortableServer\fP module for the Portable Object Adapter (POA) defines the native \f2Servant\fP type. In the Java programming language, the \f2Servant\fP type is mapped to the Java \f2org.omg.PortableServer.Servant\fP class. It serves as the base class for all POA servant implementations and provides a number of methods that may be invoked by the application programmer, as well as methods which are invoked by the POA itself and may be overridden by the user to control aspects of servant behavior. |
85 .fi |
|
86 http://java.sun.com/javase/6/docs/api/org/omg/PortableServer/Servant.html and implements the \f2InvokeHandler\fP interface and the operations interface associated with the IDL interface the skeleton implements. |
|
87 .LP |
|
88 .LP |
|
89 The \f2PortableServer\fP module for the |
|
90 .na |
|
91 \f2Portable Object Adapter (POA)\fP @ |
|
92 .fi |
|
93 http://java.sun.com/javase/6/docs/technotes/guides/idl/POA.html defines the native \f2Servant\fP type. In the Java programming language, the \f2Servant\fP type is mapped to the Java \f2org.omg.PortableServer.Servant\fP class. It serves as the base class for all POA servant implementations and provides a number of methods that may be invoked by the application programmer, as well as methods which are invoked by the POA itself and may be overridden by the user to control aspects of servant behavior. |
83 .LP |
94 .LP |
84 .LP |
95 .LP |
85 Another option for the Inheritance Model is to use the \f2\-oldImplBase\fP flag in order to generate server\-side bindings that are compatible with versions of the Java programming language prior to J2SE 1.4. Note that using the \f2\-oldImplBase\fP flag is non\-standard: these APIs are being deprecated. You would use this flag ONLY for compatibility with existing servers written in J2SE 1.3. In that case, you would need to modify an existing MAKEFILE to add the \f2\-oldImplBase\fP flag to the \f2idlj\fP compiler, otherwise POA\-based server\-side mappings will be generated. To generate server\-side bindings that are backwards compatible: |
96 Another option for the Inheritance Model is to use the \f2\-oldImplBase\fP flag in order to generate server\-side bindings that are compatible with versions of the Java programming language prior to J2SE 1.4. Note that using the \f2\-oldImplBase\fP flag is non\-standard: these APIs are being deprecated. You would use this flag ONLY for compatibility with existing servers written in J2SE 1.3. In that case, you would need to modify an existing MAKEFILE to add the \f2\-oldImplBase\fP flag to the \f2idlj\fP compiler, otherwise POA\-based server\-side mappings will be generated. To generate server\-side bindings that are backwards compatible: |
86 .LP |
97 .LP |
87 \f2idlj \fP\f4\-fclient \-fserver\fP\f2 \fP\f4\-oldImplBase\fP\f2 My.idl\fP |
98 \f2idlj \fP\f4\-fclient \-fserver\fP\f2 \fP\f4\-oldImplBase\fP\f2 My.idl\fP |
199 .LP |
210 .LP |
200 If \f2My.idl\fP also included \f2Another.idl\fP that resided in \f2/moreIncludes\fP, for example, then you would invoke the compiler with the following command: \f2idlj \fP\f4\-i /includes \-i /moreIncludes\fP\f2 My.idl\fP |
211 If \f2My.idl\fP also included \f2Another.idl\fP that resided in \f2/moreIncludes\fP, for example, then you would invoke the compiler with the following command: \f2idlj \fP\f4\-i /includes \-i /moreIncludes\fP\f2 My.idl\fP |
201 .LP |
212 .LP |
202 Since this form of include can become irritatingly long, another means of indicating to the compiler where to search for included files is provided. This technique is similar to the idea of an environment variable. Create a file named \f2idl.config\fP in a directory that is listed in your CLASSPATH. Inside of \f2idl.config\fP, provide a line with the following form: \f2includes=/includes;/moreIncludes\fP |
213 Since this form of include can become irritatingly long, another means of indicating to the compiler where to search for included files is provided. This technique is similar to the idea of an environment variable. Create a file named \f2idl.config\fP in a directory that is listed in your CLASSPATH. Inside of \f2idl.config\fP, provide a line with the following form: \f2includes=/includes;/moreIncludes\fP |
203 .LP |
214 .LP |
204 The compiler will find this file and read in the includes list. Note that in this example the separator character between the two directories is a semicolon (;). This separator character is platform dependent. On the Windows platform, use a semicolon, on the Unix platform, use a colon, etc. For more information on \f2includes\fP, read the CLASSPATH\ (Solaris) or CLASSPATH\ (Windows) documentation. |
215 The compiler will find this file and read in the includes list. Note that in this example the separator character between the two directories is a semicolon (;). This separator character is platform dependent. On the Windows platform, use a semicolon, on the Unix platform, use a colon, etc. For more information on \f2includes\fP, see the |
|
216 .na |
|
217 \f2Setting the Classpath\fP @ |
|
218 .fi |
|
219 http://java.sun.com/javase/6/docs/technotes/tools/index.html#general. |
205 .RE |
220 .RE |
206 .SS |
221 .SS |
207 Emitting Bindings for Include Files |
222 Emitting Bindings for Include Files |
208 .LP |
223 .LP |
209 .RS 3 |
224 .RS 3 |