AdironORB 1.0.0 Release Notes
=============================

This file provides information on this release of AdironORB.

Java SDK
--------

  You need Java 2 SDK, Standard Edition, Version 1.4 (or higher)
  to build and run AdironORB.

  AdironORB has been developed using J2SE Version 1.4.0, 1.4.1, and 1.4.2.
  You need at least version 1.4.0_03 or 1.4.1_01 to build AdironORB.
  If you encounter a problem in building the documentation, use the
  version 1.4.2 instead of previous versions.


Platform
--------

  AdironORB has been tested on Linux, Solaris, and Windows platforms.
  Here are a list platforms and JDKs that have been tested.

    Mandrake Linux 6.0 (Kernel 2.2.9)
    Mandrake Linux 8.1 (Kernel 2.4.8)
    Solaris 2.8
    Windows 2000 Professional
    Windows XP Home Edition

    Java 2 SDK, Standard Edition, 1.4.1_03 and 1.4.2_01


Known Interoperability Issues
-----------------------------

  AdironORB has two interoperability issues with ORBacus for Java 4.1.2.

  In the marshaling of truncatable valuetypes, AdironORB uses indirection
  for each individual truncatable RepositoryID, but ORBacus allows
  indirection only for a list of RepositoryIDs, not for each individual
  RepositoryID.

  ORBacus has a bug in the encoding of a wchar inserted into an Any. This
  bug originates from the wrong marshaling of ORBacus Any. As a result,
  the wchar encoded in the Any cannot be decoded by the AdironORB.

  IONA has fixed these issues in the ORBacus for Java 4.1.3 release.


Known Problems
--------------
   
  1. Character Set

  Some machines (such as Solaris and SuSE 8.2) use encoding other than
  ISO-8859-1 (e.g., ISO646-US, a.k.a. ASCII) as their native character set.
  This 7-bit setting causes a problem in marshaling characters that are in
  the 8-bit range (ISO-8859-1). To work around this problem, the
  "file.encoding" system property is explicitly defined as ISO-8859-1
  in the testing.

  2. Socket GC
   
  In test cases that use specific listening ports on a server ORB,
  these ports may not be immediately available for next use even after
  closing the server sockets that use these ports. In order to work around
  this infrequest problem, we add an explicit call to System.gc()
  in these tests right before opening a new server socket. See the
  ORBTestCase.java file for details.

  3. Fail to build the AdironORB manual in HTML format

  In some cases, you may receive the following error in building the
  AdironORB documentation:

  [xslt] Loading stylesheet /.../AdironORB/tools/docbook/adironorb_html.xsl
  [xslt] : Fatal Error! org.apache.xml.dtm.DTMException: No more DTM IDs
   are available Cause: org.apache.xml.dtm.DTMException: No more DTM IDs
   are available
  [xslt] Failed to process /.../AdironORB/AdironORB/doc/orb.xml

  Using J2SDK 1.4.2 instead of 1.4.1 may solve this problem. If not,
  you may try to build the documentation only for the "AdironORB" package,
  but not also the "Tools" package. You may do so by changing to the
  "AdironORB" subdirectory and execute the command for building the
  documentation.


  For any problems in building or using AdironORB, send email to
  "support@adiron.com".

  Thank you for using AdironORB.

                                           The AdironORB Project
                                          <http://www.adiron.com/>