cosNotification Release Notes

## 1 cosNotification Release Notes

### 1.1 cosNotification 1.1.3, Release Notes

#### 1.1.1 Improvements and New Features

- A user can now define the QoS EventReliability to be Persistent. Note, this is only a lightweight version and events will be lost if a proxy is terminated.
  Own id: OTP-5923

### 1.2 cosNotification 1.1.2, Release Notes

#### 1.2.1 Improvements and New Features

- Possible to configure cosNotification not to type check, by invoking corba_object:is_a/2, supplied IOR:s. When a type check fails, the feedback has been improved.
  Own id: OTP-5823 Aux Id: seq10143

### 1.3 cosNotification 1.1.1, Release Notes

#### 1.3.1 Fixed Bugs and Malfunctions

- The app-file contained duplicated modules.
  Own id: OTP-4976

### 1.4 cosNotification 1.1, Release Notes

#### 1.4.1 Improvements and New Features

- The stub/skeleton-files generated by IC have been improved, i.e., depending on the IDL-files, reduced the size of the erl- and beam-files and decreased dependencies off Orber's Interface Repository. It is necessary to re-compile all IDL-files and use COS-applications, including Orber, compiled with IC-4.2.
  Own id: OTP-4576

### 1.5 cosNotification 1.0.6, Release Notes

#### 1.5.1 Fixed Bugs and Malfunctions

- The exception CosNotifyFilter::InvalidValue, raised by the operation CosNotifyFilter::MappingFilter::add_mapping_constraints, did not contain correct data in the body. Hence, it was not possible to pass this exception to another ORB.
  Own Id: OTP-4412
- It was not possible to set the QoS property PacingInterval to zero and the default value was not compliant with the OMG specification. The default value for MaximumBatchSize have also been changed du to the same reason.
  Own Id: OTP-4413, OTP-4414

#### 1.5.2 Incompatibilities

- The default value, for the QoS properties PacingInterval and MaximumBatchSize, have been changed to zero (i.e. no timeout) and 1 respectively, which is compliant with the OMG specification.
  Own Id: OTP-4413, OTP-4414

### 1.6 cosNotification 1.0.5, Release Notes

#### 1.6.1 Fixed Bugs and Malfunctions

- If one tries to set an unavailable/incorrect property or property value, an exception is thrown. In some cases the exception was not correct, which would cause problems if communicating via IIOP.
  Own Id: OTP-4340
- When using Filter's, with the QoS OrderPolicy set to FifoOrder, and passing a sequence of structured events, they could be delivered in the wrong order.
  Own Id: OTP-4272
- If Filter's where attached to Supplier proxies it could cause the Proxy to terminate.
  Own Id: OTP-4272

### 1.7 cosNotification 1.0.4, Release Notes

#### 1.7.1 Fixed Bugs and Malfunctions

- When passing event sequences, the PushSuppliers and PullSuppliers could crash if the objects had Filter objects associated and only a subset of the sequences where approved.
  Own Id: OTP-4099
- SupplierAdmin's did not filter any events, even though Filter objects had been attached to the SupplierAdmin.
  Own Id: OTP-4098
- If one used the '_get_default_supplier_admin'/1, exported by the CosNotifyChannelAdmin_EventChannel-module, it resulted in a loop which overloaded the channel. This is no longer the case.
  Own Id: OTP-4086
- If one used the '_get_default_filter_factory'/1, exported by the CosNotifyChannelAdmin_EventChannel-module, a new instance was created each time. Now fixed.
  Own Id: OTP-4092

#### 1.7.2 Incompatibilities

- The include paths for `CosNotification.idl` have benn changed. Hence, if you include this file in your own IDL-files you must update your paths to also point to where the cosEvent IDL-files are stored.
  Own Id: OTP-4093

### 1.8 cosNotification 1.0.3, Release Notes

#### 1.8.1 Improvements and New Features

- It is now possible to start global channel factories.
  Own Id: OTP-4078
- The Orber, version 3.2.5 or later, configuration parameter orber_debug_level can now be used to generate reports when abnormal situations occurs. For more information consult the Orber User's Guide. Note, it is not recommended to use this option for delivered systems since some of the reports is not to be considered as errors. The value of orber_debug_level must be 3, or higher, for reports to be generated.
  Own Id: OTP-4077, OTP-3962

#### 1.8.2 Fixed Bugs and Malfunctions

- When using the cosEvent API accessing a cosNotification admins the objects returned by the functions obtain_push_supplier, obtain_pull_supplier, obtain_push_consumer and obtain_pull_consumer was not of the correct type. Due to the interface change it is not possible to upgrade during runtime.
  Own Id: OTP-4079

### 1.9 cosNotification 1.0.2, Release Notes

#### 1.9.1 Improvements and New Features

- First release of the cosNotification application.
  Own Id: -

Copyright © 1991-2006 Ericsson AB