Change History

This page collects information about changes which are likely to affect Java classes which use the Gesmes/TS Suite.


Version -> Next

Version 1.1.21

Version 1.1.20

Version 1.1.17

Version 1.1 beta 4


Package {@link Int.ecb.gesmescb.edifact}

This new package replaces the previous packages edifactreader and edifactwriter.

Package {@link Int.ecb.gesmescb.fame}

The package name has been changed from famewriter to fame. This package will eventually also host the classes to read from FAME.

Changes in {@link Int.ecb.gesmescb.MessageBegin}

Information about sender contacts has been added. This most importantly resulted in changes to the constructors.

The operation getMaintenanceAgency() has been renamed to {@link Int.ecb.gesmescb.MessageBegin#getMaintenanceAgencyId()}.

Added version date to StructuralDefinitions

This was necessary to allow the {@link Int.ecb.gesmescb.xml.XMLWriter} to refer to the correct version of a {@link Int.ecb.gesmescb.KeyFamily}. This implied changing the constructor. Similar changes are prepared for other StructuralDefinitions, but there tho old constructors are still available, though deprecated.

Refactored {@link Int.ecb.gesmescb.event}

The package now openly publishes the interfaces, which were changed considerably. However, due to previous precautions, the impact on other packages is fairly limited.

Made {@link Int.ecb.gesmescb.edifact.EDIFACTReader} Gesmes/TS enabled

After Gesmes/TS became official SDMX standard in April 2003, the reading software now supports it.

Allow mix of {@link Int.ecb.gesmescb.TimeSeries} and {@link Int.ecb.gesmescb.Attribute}s

As already illustrated in thoughts about future changes, now the {@link Int.ecb.gesmescb.edifact.EDIFACTWriter} can process TimeSeries and Attributes mixed arbitrarily in data messages. To do so, the latter are temporarily stored and written at the message end. Also other {@link Int.ecb.gesmescb.event.GESMESCBWriter}s should now support mixed data events. Newly developed {@link Int.ecb.gesmescb.event.GESMESCBReader}s may from now on produce mixed data sequences.

Made {@link Int.ecb.gesmescb.edifact.EDIFACTWriter} Gesmes/TS enabled

After Gesmes/TS became official SDMX standard in April 2003, also the writing software now supports it.

Do not store coding and scope in {@link Int.ecb.gesmescb.Attribute}s

Following a period of deprecation, the methods {@link Int.ecb.gesmescb.Attribute}.getScope(), {@link Int.ecb.gesmescb.Attribute}.getCoded(), and {@link Int.ecb.gesmescb.Attribute}.isCoded() have been dropped.

Note that while at it, the constructors of {@link Int.ecb.gesmescb.Attribute} were changed, too, not only dropping the scope and coding information but also changing the ordering of the other parameters.

{@link Int.ecb.gesmescb.event.GESMESTSEventBroker} contains a {@link Int.ecb.gesmescb.util.ComponentHelper}

This was done in order to put its complain method at a central location accessible by other classes. Maybe it will in future move on even further, even closer to the dispatch methods.

The visible effect of this is that the constructor now takes a name.