Advanced search

SYN-48 Possible inconsistencies when aggregating fragments

In specific cases, consuming a snapshot with sequence number n and the subsequent fragments (n+1,.., n+m) leads to different foreign data in the MIDB than consuming the snapshot n+m. Clarification…

SYN-47 Explicit Subscription for Notifications

In release 2.0, the Syndication Interface module sends notifications about new fragments or snapshots to all Syndication modules in the local copy of the SPOCS TL. As documented in D1.4 Software…

SYN-46/ESE-47 Consolidated Configuration

The modules of release 2.0 use multiple configuration files. They also use part of the syndication database for configuration. Consolidating configuration in just one or two managed objects would…

ESE-46 More Robust Retry Mechanism for Sending Notifications Remotely

The WP4 routing library that the Syndication Interface module uses for sending notifications to remote Aggregation modules simply writes failures to deliver these notifications into a retry file. The…

ESE-14 Transformation API to return entity loading status (inserted/updated/noop)

There is no way to tell from transformation API what happend with object passed to loadXXX(...) method: was it inserted/updated/no changes. For example, methods could return status code... Component…

ESE-26 More Robust Retry Mechanism for Sending Notifications Locally

The Transformation module sends a notification to the Syndication Interface module whenever it successfully updates the national information in the MIDB. This mechanism, however, is not completely…

SYN-6 The list of existing syndication servers

It is advisable to have access to the actual list of known syndication servers parameters. It should be possible to retrieve that list in the Aggregation module from the SPOCS TL. This improvement has…

SYN-44 A NonUniqueObjectException is thrown when you trying to retrieve two consecutive snapshots.

Fixed in Syndication/trunk. Component Code Category bug

SYN-43 The Admin UI returns HTTP error 500 when trying to process a notification of a fragment that is not published

The admin UI should display a user friendly message (that indicates that the fragment is not published) instead of the ugly "internal error 500" page Component Code Category bug

EDO-22 Multi-payload OCD verification is very slow due to multiple retrieving of TSL

During verification of multi-payload OCD TSL is retrieved multiple times: 1. TSL is retrieved for each payload document (should be not retrieved more than once for whole OCD) 2. For 2nd and subsequent…

EDO-23 OCDAuthenticationModule.verify() throws java.util.ConcurrentModificationException in multithreaded environment

Note that we construct new OCDAuthenticationModule for each validation: is = new FileInputStream(file); OCDAuthenticationModule module = new OCDAuthenticationModule(); Document statusDoc = module…

EDO-26 OCD verifier do not trust CA certificates registered in TSL (if CA certificate path is not in TSL)

OCD verifier should trust CA certificate if it is registered in TSL. We are trying to validate OCD signed with good real life certificate and it fails, because after verifier successfully finds CA…