SBForge parent pom

Release History

VersionDateDescription
0.4.02011-11-XXMajor xsd updates. See liste below

Release 0.4.0 - 2011-11-XX

TypeChangesBy

add

All messages now extend the either the MessageResponse or the MessageRequest super types which again extend the general Message type. Alarms extend the Message type directly.Mikis

update

AuditTrailInformation has been removed from response type messages and made optional on requests.Mikis

remove

The BitRepositoryCollections element has been removed from alarms (as alarms are local to a collection).Mikis

update

The CollectionID and ChecksumsDataForBitRepositoryFile has been renamed to CollectionID and ChecksumsDataForFile (removed trivial BitRepository).Mikis

update

Added change notes functionality to Maven site, so we can document the changes found to the protocol.Mikis

remove

Removed old AlarmCodes for "General alarm" and "Unknown user access".Kim

Added unified ResponseCode type.Kim

Added ResponseInfo element.Kim

update

Updated the various response messages to use the new unified ResponseInfo element. Effected example messages have also been updated.Kim

remove

Removed FinalReponseInfo, ProgressResponseInfo, IdentifyResponseInfo elements. Killed off old response code types (including unions).Kim

update

Made FileSize and ChecksumDataForFile optional in GetFileProgressResponse. Made ResultingChecksums optional in GetChecksumsFinalResponse.Kim

update

Made ResultingFileIDs optional in GetFileIDsFinalResponse. Made ChecksumsDataForNewFile optional in PutFileRequest. This is in accordance with the documentation text and aligned with the reference clients not delivering checksums at this point. It should be considered whether this is the wanted behavior! Made ChecksumsDataForNewFile optional in PutFileFinalResponse.Kim

Updated the values of ResponseCodes and AlarmCodes to 200, 400 and 500 series codes.Kim

Changed "calculationTimestamp" in "FileIDsDataItem" to "creationTimestamp" and updated comments to reflect its semantics.Kim