Installation guide

CHAPTER 8 New Features in EAServer 4.0
What’s New 79
Deployment and code generation performance
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:
For information on using these options when importing EAR or JAR files or
when generating Java stubs, see the online help in EAServer Manager.
Systems management enhancements
EAServer 4.0 provides automated tools for deployment, configuration, and
installation, simplifications to the server and tool scripts, and consolidation of
the run-time Java classes.
Server and EAServer Manager start-up scripts
The scripts to start EAServer Manager and the server have been simplified. For
example, one script starts servers for all JDK versions. For more information,
see the EAServer System Administration Guide.
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.