Options are preceded by a hyphen (-). For some of the options you can use the inverse of the default value by either using
-[no_] or removing the hyphen. For example, to display a “warning” if a
#pragma is not recognized, the default value is:
The idl2cs tool compiles an IDL source file and creates a directory structure containing the C# mappings for the IDL declarations. The
idl2cs and
idl2csj tools are identical except that
idl2csj will run in a Java-only environment (allowing the compiler to be run on platforms without .NET, including Unix and older Windows machines), while
idl2cs will run in a C#-only (.NET Framework) environment.
This command generates C# code from a Java class. java2cs translates a remote interface defined in Java RMI into corresponding C#. It will translate remote interfaces, EJB interfaces, and value classes into C#. Note that
java2cs will also translate types referred to directly or indirectly by the input types.
The java2cs compiler does not support overloaded methods on CORBA interfaces.
If you use a class that extends org.omg.CORBA.IDLEntity in some Java remote interface definition, it must have the following:
If you use a class that extends org.omg.CORBA.IDLEntity in some Java remote interface definition, use the
-import <IDL files
> directive in the
java2cs tool's command line.
Use java2cs if you have existing Java byte code that you wish to adapt to use distributed objects or if you do not want to write IDL. By using
java2cs, you can generate the necessary container classes, client stubs, and server skeletons from Java byte code.