Search the Community

Habari Client libraries 2021.02 Habarisoft released new versions of its Object Pascal STOMP client libraries for integration with popular open source message brokers: Habari Client for ActiveMQ 6.8 – tested with Apache ActiveMQ 5.16.0 Habari Client for Artemis 6.8 – tested with ActiveMQ Artemis 2.16.0 Habari Client for OpenMQ 6.8 – tested with Eclipse GlassFish 6.0.0 Habari Client for RabbitMQ 6.8 – tested with RabbitMQ 3.8.9 and 3.8.11 Improved map/object message transformation API Register two message transformers – one for map messages, one for object messages – on the same connection Use any custom transformation id value (transformation id’s are no longer limited to a hard-coded set) Unit tests for map message and object message transformation are included Documentation for map and object message exchange is updated The old map/object message transformation API still included, but disabled and marked as deprecated Other changes Added support for Artemis queue browser API Migrated management API client from SuperObject to JsonDataObjects Installer applications are now digitally signed Console output for unit test logging now includes test class name and test method name Removed support for OmniXML and Superobject Fixed Free Pascal 3.2.0 warnings about uninitialized values Fixed failing unit tests for Artemis Added a test for ActiveMQ queue browser API 20% to 70% discount You may purchase licenses now with a 20% discount if you use code habari202102delphi in the order form. This special offer is limited until 31 March 2021. Existing license holders with expired access to updates qualify for 30% discount. License holders within the first year after purchase qualify for 70% discount. Offer may not be combined with any other coupons, discounts, offers, or promotions. Further resources and demo applications Home page: https://www.habarisoft.com/ About Habari Client libraries Habari Client libraries enable Object Pascal applications to take advantage of message broker / message queue technology – which is distributed, loosely coupled, reliable and asynchronous – to build integrated systems, using peer-to-peer and publish-subscribe communication models.