1 <!doctype html> 2 <html> 3 <head> 4 <meta http-equiv="Content-Type" content="text/html"> 5 <title>IDL-to-Java Generated Files</title> 6 </head> 7 <body bgcolor="#FFFFFF"> 8 9 <H1>IDL-to-Java Generated Files</H1> 10 11 <P>The files that are generated by the IDL-to-Java compiler, in accordance with 12 the <em><a href="http://www.omg.org/cgi-bin/doc?ptc/00-01-08"> 13 IDL-to-Java Language Mapping Specification</a></em>, 14 which is implemented in Java<sup><font size="-2">TM</font></sup> SE 6 15 according the <a href="compliance.html">compliance</a> document. 16 17 18 <P>In general IDL names and identifiers are mapped to Java names 19 and identifiers with no change. Because of the nature of the Java language, 20 a single IDL construct may be mapped to several (differently named) Java constructs. 21 The additional names are constructed by appending a descriptive suffix. 22 For example, the IDL interface <code>foo</code> is mapped to the Java 23 interfaces <code>foo</code> and <code>fooOperations</code>, and additional 24 Java classes <code>fooHelper</code>, <code>fooHolder</code>, <code>fooPOA</code>, 25 and optionally <code>fooPOATie</code>. 26 27 28 29 <P>The mapping in effect reserves the use of several names for its own purposes. These are: 30 <UL> 31 <LI>The Java class <a href="#helper"><code><type>Helper</code></a>, 32 where <code><type></code> is the name of an IDL defined type. 33 <LI>The Java class <a href="#holder"><code><type>Holder</code></a>, 34 where <code><type></code> | 1 <!doctype html> 2 <html lang="en"> 3 <head> 4 <meta http-equiv="Content-Type" content="text/html"> 5 <title>IDL-to-Java Generated Files</title> 6 </head> 7 <body> 8 9 <H1>IDL-to-Java Generated Files</H1> 10 11 <P>The files that are generated by the IDL-to-Java compiler, in accordance with 12 the <em><a href="http://www.omg.org/cgi-bin/doc?ptc/00-01-08"> 13 IDL-to-Java Language Mapping Specification</a></em>, 14 which is implemented in Java™ SE 6 15 according the <a href="compliance.html">compliance</a> document. 16 17 18 <P>In general IDL names and identifiers are mapped to Java names 19 and identifiers with no change. Because of the nature of the Java language, 20 a single IDL construct may be mapped to several (differently named) Java constructs. 21 The additional names are constructed by appending a descriptive suffix. 22 For example, the IDL interface <code>foo</code> is mapped to the Java 23 interfaces <code>foo</code> and <code>fooOperations</code>, and additional 24 Java classes <code>fooHelper</code>, <code>fooHolder</code>, <code>fooPOA</code>, 25 and optionally <code>fooPOATie</code>. 26 27 28 29 <P>The mapping in effect reserves the use of several names for its own purposes. These are: 30 <UL> 31 <LI>The Java class <a href="#helper"><code><type>Helper</code></a>, 32 where <code><type></code> is the name of an IDL defined type. 33 <LI>The Java class <a href="#holder"><code><type>Holder</code></a>, 34 where <code><type></code> |