Description:
TIBCO Adapter for CORBA 5.1.0 Hotfix 3 is available on  
Windows 2000, Solaris 7, 8, 9 and HP-UX 11 and 11i.

This Hotfix is available only for Orbix. This HotFix is NOT cumulative.
Please apply HF2 for CORBA adapter 5.1.0 before applying HF3.
Refer to the HotFix Readme for more information.

This HotFix addresses the following issues:

* Defect Id : 1-1H8RPZ
The adapter did not use the "Interoperating ORB" field from the
repository and instead ignored it. This has been fixed.
  
* Defect Id : 1-1KBVH1
The adapter unexpectedly terminated when it received messages in the
XML wire format over the TIBCO Rendezvous transport. This has been
fixed.

* Defect Id : 1-1KBVHH
When the adapter was configured with the publication service to make
a two-way invocation, it unexpectedly terminated if the wire format
of the message being published was XML and was carried over the JMS
transport. This has been fixed.

* Defect Id : 1-1MIE7W
The adapter failed to convert an ActiveEnterprise message containing
an "any" data type, into a CORBA message when the "any" data type
contained boolean data. This has been fixed.

* Defect Id : 1-1MVGDX
The adapter unexpectedly terminated when it attempted to convert an
ActiveEnterprise message containing an "any" data type, into a CORBA
message, when the "any" value contained complex data, such as an
array, sequence, structure, or class. This has been fixed.  The
adapter no longer terminates. Instead it displays a meaningful error
message.

* Defect Id : 1-1PE2NL
When sending a request message to a CORBA server, the adapter
configured as a Subscriber or a Request-Response Server, unexpectedly
terminated if it received a user exception from the CORBA server.
This has been fixed.

* Defect Id : 1-1H8ZYL
The adapter did not process IDL attributes and CORBA anys correctly
when using Orbix 3.3.6 for C++. This has been fixed.

* Defect Id : 1-1HOYNH
The adapter terminated unexpectedly when using Orbix 3.3.6 for C++
while running the Subscription and Request-Response Server services
(SDK to CORBA scenarios). This has been fixed.

* Defect Id : 1-1JURLI
The adapter could not interoperate with the CORBA servers shipped
with the installation of Orbix 3.3.6 for C++. This has been fixed.

* Defect Id : 1-1LINRK
When an IDL file contained interfaces that were derived from other
interfaces, the adapter unexpectedly terminated during
initialization. This has been fixed.

* Defect Id : 1-1MUWBP
When the adapter received an ActiveEnterprise request message, it
unexpectedly terminated if either its, or the CORBA server's Orbix
daemon was not running. This has been fixed.

* Defect Id : 1-1HP3D5, 1HCOOD
When the adapter was installed to work with a specified ORB, the ORB-
specific adapter libraries that were installed did not contain any
ORB-specific information. This prevented users from identifying the
type of installation. This has been fixed. ORB-specific adapter
libraries now contain ORB-specific information that users can read.
This information includes the ORB type and ORB version that were used
to build the ORB-specific adapter library. Users can read this
information using the following commands:
  
On Microsoft Windows:
* Right-click on the library.
* Select the "Properties" option.
* Click the "Version" tab.
* Select "ORBType" in the left-hand side pane from "Other Version
   Information".
* The ORB type and version are displayed in the right-hand side pane.
  
On UNIX:
* At the command prompt execute the ‘what’ command on the .so
   component. For example: $what libCorbautil.so|grep libCorbautil.
   This will display the ORB and version information.
  
   OR
  
* At the command prompt execute the ‘strings’ command on the .so
   component. For example: $strings libCorbautil.so|grep libCorbautil.
   This will display the ORB and version information.
  
* Defect Id : 1-1TA8GF
When an IDL file contained an interface that was derived from a base
interface, the adapter could not invoke methods that were defined in
the base interface. Instead, it could only invoke methods that were
defined in the derived interface.
This has been fixed. The adapter can now invoke methods that have
been defined in the base interface and the derived interface.


Known Issues in 5.1.0.14 Hotfix3 :

* Defect Id : 1-1OIN91
The adapter cannot retrieve correct IDL information from the
Interface Repository when the Interface Repository is not the one
shipped with IONA's Orbix 3.3.6 for C++.

* Defect Id : 1-1P8OJ7
When the adapter is used with Orbix 3.3.6 for C++, there are per-
invocation memory leaks in the adapter.

* Defect Id : 1-1P8OJR
The adapter on Solaris has only been integrated with Orbix 3.3.6 for
Solaris 7. Orbix 3.3.6 for Solaris 7 must also be used on Solaris 8.
Although there is a different version of Orbix 3.3.6 that is meant
purely for Solaris 8, the adapter has not been integrated or tested
with it.

* Defect Id : 1-1RXUA5
The adapter cannot convert a TIBCO message into a CORBA request if
the schema of the TIBCO message contains optional fields that are set
to NULL. This is because the NULL optional fields are not present in
the message, and therefore the schema of the TIBCO message does not
match the schema expected by the adapter.

This is not a defect in the adapter because the CORBA specification
does not permit the use of optional or NULL fields in IDL files.
Therefore, a TIBCO message cannot contain optional or NULL fields.
The TIBCO message must explicitly contain every field that is
expected by the IDL file.

* Defect Id : 1-1RXUAI
The adapter cannot convert a CORBA message into a TIBCO message and
vice versa if the CORBA message contains complex or user-defined
CORBA data that is embedded in a CORBA any data type.

The workaround is to ensure that the CORBA any data type in the CORBA
message contains only CORBA primitive or scalar data.

OR

Replace the CORBA any data type in the IDL file with the schema of
the complex or user defined data type.

* Defect Id : 1-1E2JJF
When an IDL file contains errors, the IDL to Schema converter does
not report the correct file name, line number and type of error that
it encounters when parsing the IDL file

* Defect Id : 1-1WOOYF
When an IDL file contains references to CORBA octet data types, the
IDL to Schema converter does not convert the octets to TIBCO binary
types. Instead, CORBA octets are converted to unknown types

The workaround is to manually modify the schema in the TIBCO
repository so that CORBA octets are mapped to TIBCO binary types

* Defect Id : 1-1YCO5P
When importing an IDL file into TIBCO Designer, if the IDL file
contains a "#if" of #elif" preprocessor definition, the IDL to Schema
tab in the adapter palette displays an error and does not generate
the schema. These preprocessor definitions are not supported by the
CORBA adapter's IDL to Schema converter

The workaround is to preprocess the IDL file using one of the
following compilers:
   * IONA ORBacus 4.1.2 for C++ IDL compiler
   * IONA ORBacus 4.1.2 for Java IDL compiler
   * IONA Orbix 3.3.6 for C++ IDL compiler
   * Borland VisiBroker 4.5 for C++ IDL compiler
   * Borland VisiBroker 5.2 for C++ IDL compiler
   * Microsoft Visual C++ 6.0's cl compiler
This will generate a preprocessed IDL file that will not contain any
preprocessor definitions. Use the preprocessed IDL file to generate
the schema

* Defect Id : 1-1YCO66
When importing an IDL file into TIBCO Designer, if the IDL file
contains a floating point literal with an exponent such as -1.42E+86,
the IDL to Schema tab in the adapter palette displays an error and
does not generate schema. This literal format is not supported by the
CORBA adapter's IDL to Schema converter

The workaround is to replace the floating point exponent value with a
simple floating point literal value

* Defect Id : 1-1YCO6N
When importing an IDL file into TIBCO Designer, if the IDL file
contains an arithmetic expression such as "const long c1 = 5 + 2;",
the IDL to Schema tab in the adapter palette displays an error and
does not generate schema. Evaluation of arithmetic expressions in IDL
files is not supported by the CORBA adapter's IDL to Schema converter

The workaround is to replace the arithmetic expression in the IDL
file with the evaluated value. For example, replace
"const long c1 = 5 + 2;"
with
"const long c1 = 7;"

* Defect Id : 1-1YCO74
When importing an IDL file into TIBCO Designer, if the IDL file
contains an anonymous complex data type such as a structure, sequence
or array, the IDL to Schema tab in the adapter palette displays an
error and does not generate the schema. Anonymous complex data types
are not supported by the CORBA adapter's IDL to Schema converter

The workaround is to convert anonymous types into specific types. For
example convert:
   //Anonymous sequence
   sequence&ltInvocable> composition_;
into:
   //Specific sequence
   typedef sequence&ltInvocable> InvocableList;
   InvocableList composition_;

* Defect Id : 1-1YCO7P
When importing an IDL file into TIBCO Designer, if the IDL file
contains a forward declared interface that has either been re-defined
elsewhere in the same IDL file or in an included IDL file, the IDL to
Schema tab in the adapter palette displays an error and does not
generate schema. Multiple forward declarations are not suppoted by
the CORBA adapter's IDL to Schema converter

The workaround is to ensure that an interface is forward-declared
only once in an IDL file or a group of IDL files

* Defect Id : 1-1YCXH6
When importing an IDL file into TIBCO Designer, if the IDL file
contains macro definitions the IDL to Schema tab in the adapter
palette displays an error and does not generate schema. Macro
defintion and expansion is not supported by the CORBA adapter's IDL
to Schema converter

The workaround is to preprocess the IDL file using one of the
following compilers:
   * IONA ORBacus 4.1.2 for C++ IDL compiler
   * IONA ORBacus 4.1.2 for Java IDL compiler
   * IONA Orbix 3.3.6 for C++ IDL compiler
   * Borland VisiBroker 4.5 for C++ IDL compiler
   * Borland VisiBroker 5.2 for C++ IDL compiler
   * Microsoft Visual C++ 6.0's cl compiler
This will generate a preprocessed IDL file that will not contain any
macro definitions. Use the preprocessed IDL file to generate the
schema

* Defect Id : 1-1RPDKY
When a hotfix containing a new CORBA adapter palette is installed,
TIBCO Designer cannot locate and identify the new CORBA adapter
palette, and instead continues to use the previous palette.

The workaround is to manually modify Designer's TRA file to include
the new palette

This hot fix can be downloaded from the TIBCO Product
Support ftp server, ftp://support-ftp.tibco.com/, using your
username and password for the TIBCO Support Web. Once
logged on, you can find the hot fix under:
available_downloads/ActiveEnterprise/Adapters/CORBA/5.1.0/hotfix-3/

Please contact TIBCO Support if you have any problems
finding or downloading this hot fix.