Orber Release Notes

## 1 Orber Release Notes

### 1.1 Orber 3.6.3

#### 1.1.1 Improvements and New Features

- When installing Orber it is now possible to set the priority for Orber internal Mnesia tables. For more information, see the Reference Manual regarding orber:install/2.
  Own Id: OTP-5907 Aux Id: seq10156
- The operation corba_object:is_a/2/3 now only connect to a remote if necessary (i.e. the target object inherits from objects associated with the given IFR id.
  Own Id: OTP-5908

#### 1.1.2 Fixed Bugs and Malfunctions

- The operation corba_object:is_remote/1 always returned true, which was introduced in orber-3.2.10.
  Own Id: OTP-5909

### 1.2 Orber 3.6.2

#### 1.2.1 Improvements and New Features

- Native interceptors may now export new_in_connection and new_out_connection operations with arity 5. If this is the case, information about the local interface and port is passed to the interceptor. Orber's built in interceptors have been changed to include this information as well.
  Own Id: OTP-5671

#### 1.2.2 Fixed Bugs and Malfunctions

- In some cases, e.g. incorrect GIOP headers or a CancelRequest containing a non-existing RequestId, the incoming connection would be terminated.
  Own Id: OTP-5672 Aux Id: seq10037
- If combining the 'Use Current Interface in IOR' and 'Use IPv6' flags, exported IOR:s conatined an incorrect host address.
  Own Id: OTP-5673

### 1.3 Orber 3.6.1

#### 1.3.1 Improvements and New Features

- Reduced overhead when using outgoing ACL with a local interface defined.
  Own Id: OTP-5659
- Added guards to ensure that, when so required, a list of IOP_ServiceContext's is passed instead of, for example, just the context record.
  Own Id: OTP-5660

#### 1.3.2 Fixed Bugs and Malfunctions

- The documentation referred to two different context definitions, the incorrect ServiceContext and the correct IOP_ServiceContext. The hrl file PATH/include/corba.hrl also contained the incorrect record definition. This has now been updated so that only IOP_ServiceContext is used and referred to.
  Own Id: OTP-5658

### 1.4 Orber 3.6

#### 1.4.1 Improvements and New Features

- It is now possible to define a Access Control List (ACL), which limits the host and ports Orber may connect to or accept connections from.
  Own Id: OTP-5567
- It is now possible to add, and remove, listen interfaces. For more information, consult the User's Guide and the orber module Reference Manual.
  Own Id: OTP-5568
- It is now possible to activate and deactivate Audit/Trail logging. One of the three built in interceptors will be used depending on the requested verbosity.
  Own Id: OTP-5569
- It is now possible to configure Orber to add the interface, to exported local IOR:s, a Request came via.
  Own Id: OTP-5570
- It is now possible to instruct Orber which local interface an outgoing Request shall be sent via. To accomplish this the Orber generic context must be added added to each invocation.
  Own Id: OTP-5571
- It is now possible to define a default local interface, which Orber will use when connecting to another ORB.
  Own Id: OTP-5583

For information about older versions see release notes history.

Copyright © 1991-2006 Ericsson AB