[Erlang Systems]

1 Orber Release Notes

1.1 Orber 3.2.9, Release Notes

1.1.1 Improvements and new features

-

1.1.2 Fixed bugs and malfunctions

1.1.3 Incompatibilities

-

1.1.4 Known bugs and problems

1.2 Orber 3.2.8, Release Notes

1.2.1 Improvements and new features

1.2.2 Fixed bugs and malfunctions

-

1.2.3 Incompatibilities

-

1.2.4 Known bugs and problems

1.3 Orber 3.2.7, Release Notes

1.3.1 Improvements and new features

1.3.2 Fixed bugs and malfunctions

1.3.3 Incompatibilities

-

1.3.4 Known bugs and problems

1.4 Orber 3.2.6, Release Notes

1.4.1 Improvements and new features

1.4.2 Fixed bugs and malfunctions

1.4.3 Incompatibilities

-

1.4.4 Known bugs and problems

1.5 Orber 3.2.5, Release Notes

1.5.1 Improvements and new features

1.5.2 Fixed bugs and malfunctions

1.5.3 Incompatibilities

1.5.4 Known bugs and problems

1.6 Orber 3.2.4, Release Notes

1.6.1 Improvements and new features

-

1.6.2 Fixed bugs and malfunctions

1.6.3 Incompatibilities

1.6.4 Known bugs and problems

1.7 Orber 3.2.3, Release Notes

1.7.1 Improvements and new features

1.7.2 Fixed bugs and malfunctions

1.7.3 Incompatibilities

-

1.7.4 Known bugs and problems

1.8 Orber 3.2.2, Release Notes

1.8.1 Improvements and new features

1.8.2 Fixed bugs and malfunctions

1.8.3 Incompatibilities

-

1.8.4 Known bugs and problems

1.9 Orber 3.2.1, Release Notes

1.9.1 Improvements and new features

1.9.2 Fixed bugs and malfunctions

-

1.9.3 Incompatibilities

-

1.9.4 Known bugs and problems

1.10 Orber 3.2, Release Notes

1.10.1 Improvements and new features

1.10.2 Fixed bugs and malfunctions

1.10.3 Incompatibilities

-

1.10.4 Known bugs and problems

1.11 Orber 3.1.8, Release Notes

1.11.1 Improvements and new features

1.11.2 Fixed bugs and malfunctions

1.11.3 Incompatibilities

-

1.11.4 Known bugs and problems

1.12 Orber 3.1.7, Release Notes

1.12.1 Improvements and new features

1.12.2 Fixed bugs and malfunctions

1.12.3 Incompatibilities

1.12.4 Known bugs and problems

1.13 Orber 3.1.6, Release Notes

1.13.1 Improvements and new features

1.13.2 Fixed bugs and malfunctions

-

1.13.3 Incompatibilities

-

1.13.4 Known bugs and problems

1.14 Orber 3.1.5, Release Notes

1.14.1 Improvements and new features

-

1.14.2 Fixed bugs and malfunctions

1.14.3 Incompatibilities

-

1.14.4 Known bugs and problems

1.15 Orber 3.1.4, Release Notes

1.15.1 Improvements and new features

1.15.2 Fixed bugs and malfunctions

1.15.3 Incompatibilities

1.15.4 Known bugs and problems

1.16 Orber 3.1.3, Release Notes

1.16.1 Improvements and new features

-

1.16.2 Fixed bugs and malfunctions

1.16.3 Incompatibilities

-

1.16.4 Known bugs and problems

1.17 Orber 3.1.2, Release Notes

1.17.1 Improvements and new features

-

1.17.2 Fixed bugs and malfunctions

1.17.3 Incompatibilities

The change in InitialReferences.idl to clash with the Corba standard implies changes in code that use this interface. See the OTP-3468 and OTP-3155 in the Fixed bugs and malfunctions chapter above.

1.17.4 Known bugs and problems

1.18 Orber 3.1.1, Release Notes

1.18.1 Improvements and new features

-

1.18.2 Fixed bugs and malfunctions

1.18.3 Incompatibilities

-

1.18.4 Known bugs and problems

1.19 Orber 3.1, Release Notes

1.19.1 Improvements and new features

1.19.2 Fixed bugs and malfunctions

1.19.3 Incompatibilities

-

1.19.4 Known bugs and problems

1.20 Orber 3.0.1, Release Notes

1.20.1 Improvements and new features

1.20.2 Fixed bugs and malfunctions

-

1.20.3 Incompatibilities

-

1.20.4 Known bugs and problems

1.21 Orber 3.0, Release Notes

1.21.1 Improvements and new features

1.21.2 Fixed bugs and malfunctions

1.21.3 Incompatibilities

1.21.4 Known bugs and problems

1.22 Orber 2.2.2, Release Notes

1.22.1 Improvements and new features

-

1.22.2 Fixed bugs and malfunctions

1.22.3 Incompatibilities

-

1.22.4 Known bugs and problems

1.23 Orber 2.2.1, Release Notes

1.23.1 Improvements and new features

1.23.2 Fixed bugs and malfunctions

1.23.3 Incompatibilities

The change in InitialReferences.idl to follow the Corba standard implies changes in code that use this interface. See the OTP-3155 in the Fixed bugs and malfunctions chapter above.

1.23.4 Known bugs and problems

1.23.4.1 ORB

1.23.4.2 Interface Repository

1.23.4.3 Resolving initial reference from C++

The returned IOR is the same for both C++ and Java. However, we have only tested on a client implemented in C++. That is an Orbix C++ client accessing an Orber server.

1.24 Orber 2.2, Release Notes

1.24.1 Improvements and new features

1.24.2 Fixed bugs and malfunctions

-

1.24.3 Incompatibilities

1.24.4 Known bugs and problems

1.24.4.1 ORB

1.24.4.2 Interface Repository

1.24.4.3 Resolving initial reference from C++

The returned IOR is the same for both C++ and Java. However, we have only tested on a client implemented in C++ ie.an Orbix C++ client accessing an Orber server.

1.25 Orber 2.1, Release Notes

1.25.1 Improvements and new features

In this version of Orber we have added IIOP 1.1, not all types but the protocol headers should be handled correct. IIOP 1.0 is still the default protocol so orber is fully compatible with previous version, but in OTP R5A IIOP 1.1 will be default protocol (it will be possible to configure the system for 1.0).

1.25.2 Fixed bugs and malfunctions

1.25.3 Incompatibilities

-

1.25.4 Known bugs and problems

1.25.4.1 ORB

1.25.4.2 Interface Repository

1.25.4.3 Resolving initial reference from C++

The returned IOR is the same for both C++ and Java. However, we have only tested on a client implemented in C++ ie.an Orbix C++ client accessing an Orber server.

1.26 Orber 2.0.2, Release Notes

1.26.1 Improvements and new features

-

1.26.2 Fixed bugs and malfunctions

1.26.3 Incompatibilities

-

1.26.4 Known bugs and problems

1.26.4.1 ORB

1.26.4.2 Interface Repository

1.26.4.3 Resolving initial reference from C++

The returned IOR is the same for both C++ and Java. However, we have only tested on a client implemented in C++ ie.an Orbix C++ client accessing an Orber server.

1.27 Orber 2.0.1, Release Notes

1.27.1 Improvements and new features

-

1.27.2 Fixed bugs and malfunctions

1.27.3 Incompatibilities

-

1.27.4 Known bugs and problems

1.27.4.1 ORB

1.27.4.2 Interface Repository

1.27.4.3 Resolving initial reference from C++

The returned IOR is the same for both C++ and Java. However, we have only tested on a client implemented in C++ ie.an Orbix C++ client accessing an Orber server.

1.28 orber 2.0, Release Notes

1.28.1 Improvements and new features

1.28.2 Fixed bugs and malfunctions

1.28.3 Incompatibilities

1.28.4 Known bugs and problems

1.28.4.1 ORB

1.28.4.2 Interface Repository

1.28.4.3 Resolving initial reference from C++

The returned IOR is correct and the same as for the java implementation but we have for the moment just tested with a client implemented in C++, ie an Orbix C++ client accessing an Orber server.

1.29 Orber 1.0.3, Release Notes

1.29.1 Fixed bugs and malfunctions

1.29.2 Incompatibilities

One needs to recompile the IDL files to get the inherited interfaces correctly in the IFR register/unregister functions.

1.29.3 Known bugs and problems

1.29.3.1 ORB

1.29.3.2 IDL compiler

1.29.3.3 Interface Repository

1.29.3.4 Resolving initial reference from C++

The returned IOR is correct and the same as for the java implementation but we have for the moment just tested with a client implemented in C++, ie an Orbix C++ client accessing an Orber server.

1.30 Orber 1.0.2, Release Notes

1.30.1 Fixed bugs and malfunctions

1.30.2 Incompatibilities

One needs to recompile the IDL files to get the corrections in some cases.

There are one incompatibility, the package name for the Java InitialReferences class has been changed. see bugfix id OTP-2069 above.

1.30.3 Known bugs and problems

1.30.3.1 ORB

1.30.3.2 IDL compiler

1.30.3.3 Interface Repository

1.30.3.4 Resolving initial reference from C++

The returned IOR is correct and the same as for the java implementation but we have for the moment just tested with a client implemented in C++, ie an Orbix C++ client accessing an Orber server.

1.31 Orber 1.0.1, Release Notes

1.31.1 Fixed bugs and malfunctions

1.32 Orber 1.0, Release Notes

1.32.1 Improvements and new features

Orber is a new application which allows OTP applications to interact with other programs written in other languages through the CORBA standard.

The orber release contains the following parts:

Implemented work packages are: OTP-1508, OTP-1509 (not typed event).

1.32.1.1 Orb kernel and IIOP support

There is an ORB kernel with IIOP support which allows creating persistent server objects in Erlang and access them from Erlang and java. For the moment one need a java enabled Orb to generate java from idl and use java server objects (we have tested with OrbixWeb).

1.32.1.2 IDL compiler

The IDL compiler generates server behaviours and client stubs according to the IDL to Erlang mapping. Interface inheritance is supported. The idl compiler requires gcc because it's used as preprocessor. (It's possible to run the compiler without preprocessor if for example you don't use include statements)

1.32.1.3 Interface Repository

The Interface Repository (IFR) is fully implemented. The module orber_ifr is the interface to it. The IFR is used for some type checking when coding/decoding IIOP and therefore all interfaces must be registered in the IFR.

1.32.1.4 Orber CosNaming service

This is the first version of the CosNaming compliant service which also includes two modules lname and lname_component which supports the naming library interface in erlang.

1.32.1.5 Orber CosEvent Service

Orber contains an Event Service that is compliant with the untyped part of the CosEvent service specification.

1.32.1.6 Resolving initial reference from Java

A class with just one method which returns an IOR on the external string format to the INIT object (see "Interoperable Naming Service" specification).

1.32.1.7 Resolving initial reference from C++

A class (and header file) with just one method which returns an IOR on the external string format to the INIT object (see "Interoperable Naming Service" specification).

1.32.1.8 A small example

A small programming example is contributed which shows how Orber can be used. It is an implementation of a Stack service which shows how Erlang services can be accessed from both Erlang and java.

1.32.2 Fixed bugs and malfunctions

-

1.32.3 Incompatibilities

-

1.32.4 Known bugs and problems

1.32.4.1 General

1.32.4.2 ORB

1.32.4.3 IDL compiler

1.32.4.4 Interface Repository

1.32.4.5 Resolving initial reference from C++

The returned IOR is correct and the same as for the java implementation but we have for the moment just tested with a client implemented in C++, ie an Orbix C++ client accessing an Orber server.


Copyright © 1991-2001 Ericsson Utvecklings AB