13.0.0

13.0.0 (2022-04-10)

Dependencies

• solace-message-client: update @solace-community/angular-solace-message-client to Angular 13 and migrate to RxJS 7.5 (4d5029f), closes #34

BREAKING CHANGES

• solace-message-client: updating @solace-community/angular-solace-message-client to Angular 13 and RxJS 7.5 introduced a breaking change.

  To migrate:

  • update your application to Angular 13; for detailed migration instructions, refer to https://github.com/angular/angular/blob/master/CHANGELOG.md.
  • migrate your application to RxJS 7.5; for detailed migration instructions, refer to https://rxjs.dev/6-to-7-change-summary.
  • update @scion/toolkit to version 13; for detailed migration instructions, refer to https://github.com/SchweizerischeBundesbahnen/scion-toolkit/blob/master/CHANGELOG.md.

12.0.1

12.0.1 (2021-11-15)

Features

• solace-message-client: allow controlling if to receive messages outside the Angular zone (6399eca), closes #30

12.0.0

12.0.0 (2021-09-08)

Chore

• solace-message-client: update @solace-community/angular-solace-message-client to Angular 12 (913ae8a)

11.0.1

11.0.1 (2021-08-20)

Bug Fixes

• solace-message-client: disconnect from the broker gracefully (c66c154)
• testapp: mask password field (9494653)

Code Refactoring

• solace-message-client: remove automatic marshalling of message payload into JSON (f40d0cb)

Features

• solace-message-client: add convenience API for passing and receiving message headers (d6450da)
• solace-message-client: add Solace typedef for Session, MessageConsumer, QueueBrowser, and related objects (2e3b8ab)
• solace-message-client: allow browsing messages in a queue, without removing/consuming the messages (c3bc031)
• solace-message-client: allow consuming messages sent to a queue or topic endpoint (b377ed5)
• solace-message-client: allow intercepting a message before sending it to the broker (df8e7ad)
• solace-message-client: notify when actually subscribed to a destination (245697e), closes #16
• solace-message-client: provide access to the message consumer object if connecting to a queue or topic endpoint (b37c0bf)
• solace-message-client: resolve guaranteed messaging promise after acknowledged by the broker (15fc874)
• solace-message-client: support sending messages to a queue (ab901cd)
• testapp: add toggle to follow message tail (55a517d)
• testapp: allow sending empty messages (9c260e8)
• testapp: display content of zipped messages (a119c65)
• testapp: display message content in a viewport (db13feb)
• testapp: log error when the connection to the broker fails (64052ff)
• testapp: persist session connect properties in local storage (59d328f)
• testapp: retry connecting during initial connection setup (cdf1ebe)

BREAKING CHANGES

• solace-message-client: Refactoring the API for publishing messages introduced following breaking change:

  • message payload is no longer automatically marshalled to JSON;
  • removed option to set the message body format; instead, it is derived from passed data automatically;
    if passing structured data in the form of a SDTField, data is transported as structured message of the type
    TEXT, MAP, or STREAM, or as binary message otherwise;
  • removed RxJS operator mapToObject for unmarshalling received JSON data;

  To migrate:

  • to send JSON serialized data (formerly via MessageBodyFormat.JSON or by default), you need to pass serialized data instead of the object literal;
  • to send a structured text message (formerly via MessageBodyFormat.TEXT), add transfer data to a SDTField of the type STRING, as following: solaceMessageClient.publish('topic', SolaceObjectFactory.createSDTField(SDTFieldType.STRING, 'payload'));
  • to send binary data (formerly via MessageBodyFormat.BINARY), pass transfer data either as string, array buffer like object, or data view instead;
  • if used a format function to convert data into a structured container (Structured Data Type), pass transfer data in the form of a SDTField instead;
  • if used mapToObject RxJS operator to unmarshall received JSON data into a JavaScript object literal, you need to unmarshall received data yourself;

11.0.0

11.0.0 (2021-03-18)

Bug Fixes

• solace-message-client: do not lose subscription when a topic is re-subscribed in quick succession (659ee26), closes #7

Features

• solace-message-client: initial contribution of Angular Solace Message Client library (d5b275b)