EAServer 4.0 introduces Java-to-IDL and IDL-to-Java code generation optimizations. These optimizations can increase your productivity when you deploy Java based applications with complicated component class hierarchies and when you generate Java stubs for these applications.
The J2EE EAR importer, EJB JAR importer, and the Java code generator have been enhanced to allow you to specify a code generation strategy as described in the following table:
Generation strategy |
Specifies |
|---|---|
Full |
Always generates Java or IDL types for every interface and type. |
Incremental |
Compares IDL and Java timestamps to determine whether new versions must be generated. Java timestamps are maintained in a database in the EAServer repository. |
Optimistic |
Similar to Incremental, except that the check for changed types in each IDL module or Java package ends if the first comparison indicates no change. |
For information on using these options when importing EAR or JAR files or when generating Java stubs, see the online help in EAServer Manager.
