CORBA 2.3 Update 3 README

7) The NS CORBA IDL compiler generates code only for top-level
IDL files. Code is not generated for IDL files that are
included using a #include directive.
(SOLN 10-011009-3656)
8) The NonStop Distributed Component Console is used to set the
tracing options for the OTS TM, first to "detailed", and then
to "none". Trace records are generated when the OTS TM has
tracing set to "detailed". When the tracing options are reset
to "none", not all of the tracing options are reset. This
causes some ORB messages to continue to be generated for the
OTS TM.
(SOLN 10-011015-3813)
9) The CORBA Workstation Installer is unable to access the install
log when the owner of the java directory is different from the
owner of the nscorba directory, and the default security for new
files causes the log file to be unwriteable after the installer
admin logs on as the java owner.
When the GUI installer detects that NonStop Java is owned by
another user, a dialog box is displayed to enter the user name
and password for the NonStop Java owner. Before continuing,
obtain access to the NonStop Guardian CORBA sub volume
($SYSTEM.ZORBSDK or $SYSTEM.ZORBRTK, by default) and FUP SECURE
the file named "LOG" as "NNNU". The GUI installation may now be
continued by entering the user name and password and selecting OK
to finish the installation successfully.
(SOLN 10-011016-3851)
10) NSots logs a few informational messages with an EMS error label.
(SOLN 10-011016-3852)
X. New Features in this Release
1) During the tracing of GFSIOP file system protocol event
framework receive messages, the device name used during an
an open was not recorded. The trace message was enhanced to
record the name of the device. This helps to identify
problems such as a FENOSUCHDEV, the no such device error
message. The tracing messages were enhanced in both the
C++ and Java ORBs.
2) Bootstrap Daemon support was added to support
interoperability as described below.
The Bootstrap protocol is documented in section 3 of the
Interoperable Naming Service Specification (97-06-03).
Any client ORB must obtain the initial root naming context on an
arbitrary host in an interoperable fashion. Using a file system
relies on the presence of a shared file system, and an agreed to
location. These specific and often platform dependent mechanisms
prevent all clients from obtaining the root naming context in a
portable and interoperable way.
file:///C|/Corba Readmes/ReadmeCORBA23u3.txt
file:///C|/Corba Readmes/ReadmeCORBA23u3.txt (10 of 15) [4/27/2004 11:41:35 AM]