Appendix E Using the Command Line IDL Compiler

You can use EAServer's command-line IDL compiler to generate stubs, skeletons, and ActiveX type library and registration files. You can also use Jaguar Manager to perform these tasks. The command-line compiler is useful in environments where the generation of files must be automated.

   Do you know about jagtool and jagant? The jagtool utility, provided in EAServer 4.0 and later versions, also supports stub and skeleton generation from the command line, as well as common management tasks such as setting component properties. The jagant utility provides the same functionality, but can be run from Jakarta Ant build files. See the EAServer System Administration Guide for information on these utilities.

Requirements

The IDL compiler must be run from EAServer installation that contains the configuration repository for your components. The IDL compiler is a Java application and must be run by a version 1.2 or later Java virtual machine. These EAServer JAR files must be in the CLASSPATH:

• java/lib/easclient.jar
• java/lib/easserver.jar
• java/lib/easj2ee.jar

com.sybase.CORBA.idl.Compiler

Description

Generates EAServer proxies or component skeletons for interfaces and datatypes defined in CORBA IDL.

Syntax

com.sybase.CORBA.idl.Compiler prefix-opts idl-files format-opts suffix-opts

• prefix-opts Is a list of one or more of these options:

  Option	Explanation
  -v	Run in verbose mode.
  -i folder	Add folder for IDL include files. The default is the EAServer Repository/idl subdirectory.
  -r folder	Required. Specify the location of the EAServer Repository subdirectory, for example, d:\EAServer\Repository.
  -lang language	Specify a language for error messages. Possible values are: us_english - The default. english japanese german french korean chinese

• idl-files Is a list of one or more IDL module files, separated by spaces. Nested IDL modules are organized in nested directories; you must specify the path to a nested module relative to the EAServer Repository/idl subdirectory. For example, the file name that defines module com::foo::bar is com/foo/bar.idl.
• format-opts is a list of one or more of the following options:

  Option	Explanation
  -cr	Use CR/LF in generated files.
  -f folder	Specify base folder for code generation.
  -p folder	Specify location of jagproxy.dll for generation of ActiveX type library and Registry files.
  -jp IM=JP	Set Java package JP for IDL module IM, for example: -jp com::foo::bar=com.foo.bar The specified package overrides the default (see "Specifying Java package mappings for IDL modules").
  -jv version	Set Java version for code generation. The Java version affects only EJB stubs, specifically it configures the default for finder methods that return multiple keys and lack an IDL directive to specify the Java return type. See "Generating EJB stubs" for more information.
  -nh	Suppress generation of Java helper and holder classes.
  -np	Suppress module prefix for PowerBuilder stubs.

• target-opts is a list of one or more of the following options:

  Option	Explanation
  -cpp	Generate C++ stubs following CORBA 2.3 C++.language bindings specification.
  -java	Generate Java stubs following CORBA 2.3 Java.language bindings specification.
  -ejb	Generate EJB 1.0 Java stubs.
  -jdbc	Generate code for EAServer 1.1 / JDBC stubs.
  -pb	Generate code for CORBA 2.3 / PowerBuilder.
  -idl	Generate pretty-printed IDL output.
  -reg load	Generate REG file and optionally load into registry. -reg load generates loads the REG file. -reg load generates and does not load.
  -tlb save	Generate TLB file and optionally save generated MIDL. -tlb nosave generates TLB and deletes the intermediate MIDL file. -tlb save generates TLB and keeps the MIDL file.
  -skeleton Pack/Comp	Generate a skeleton for EAServer component Pack/Comp, where Pack is the EAServer package, and Comp is the component name as displayed in Jaguar Manager.