Release Date: Wednesday, November 11, 2015. This is the first release of Eagle 1.3, released as part of the X Platform 3.0.0 Platform Release
Release Highlights
Change Log
New Feature
|
Prior to this release, Eagle applications had limited visibility into what the service dispatch layer is doing. This release implements callouts made by the Eagle service layer that can be overriden by the application main class to gain visibility into the actions being performed by the service layer. The following callouts are implemented:
|
|
This release implements support to journal message processing stats to a transaction log. The journalling is done using an X Blogger thus keeping the size of the log bounded while allowing for the log to be tailed i.e. CDCd for siphoning of the message processing stats entries to other places of long term storage e.g. RDBMS for deeper analysis |
Improvement
|
Due to the nature of request reply of an Eagle client, outbound and inbound messages need not be marked as read only. Additionally, the Eagle client does need to modify sent or received messages. This release forcibly sets the nv.aep.inbound.setasreadonly and nv.aep.outbound.setasreadonly parameters to false to prevent outbound and inbound messages to be set as read-only |
Change
|
To avoid schema collisions and confusion the eagle service model schema was updated from 'http://www.neeveresearch.com' which conflicts with the current adm schema to 'http://www.neeveresearch.com/schema/x-asml' This requires a changing model files that use the old schema namespace |
Bug
|
The client code generated by Eagle ASM attempts to modify the header of a request message upon receipt of the reply. With the change in 1.8 to make outbound messages readonly after send, this causes the Eagle generated client to throw a 'node is read only' error since the outbound message has been made read only. This release fixes this issue. |
|
This fix resolves an issue in percentile calculations for request processing and queue times. |
