Last modified 11 years ago

Changelog

version 3.0.3 / 21/05/2013 /

  • New configuration option for disabling CurrentMessages.
  • Fixed memory leak related to not freeing the fault data.
  • Other minor corrections.

version 3.0.2 / 14/05/2013 /

  • Updated the database configuration script

version 3.0.1 / 13/05/2013 /

  • WorkingDirectory location changed to the $localstate/log/qcg/qcg-ntf directory (in the service config file)

version 3.0.0 / 18/04/2013 /

  • No changes - just update to the new major release "3".

version 2.6.4 [26 Mar 2012]

  • Changed the default logging level from DEBUG to INFO and tuned the logging messages.
  • Changed the type of the fault for GetCurrentMessage returned when there is no database connection. Now the returned type is in accordance with the WS-Notification standard (NoCurrentMessageOnTopic).
  • Fixed validation of TopicExpressions for Simple and Concrete Topic dialects.
  • Fixed MySQL interactions.

version 2.6.3 [31 May 2012]

  • Fixed XMPP publisher plugin to use the provided address of XMPP server instead of extracted from JID; XMPP server set to NULL enables automatic selection based on JID.

version 2.6.2 [16 April 2012]

  • Added options to the configuration file for adjustment of the format of the Topic element in Notify messages sent by the publisher modules.
  • Changed default values for some configuration options. Among others, the time checking is now enabled by default.
  • Bugs fixes.

version 2.6.1 [30 March 2012]

  • Modified XMPP publisher module to support XSLT transformations and sending messages as a "chat".
  • Fixed logging.

version 2.6.0 [24 February 2012]

  • Implemented functions for XSLT documents management.
  • Implemented SMTP publisher module. The module utilizes XSLT documents to translate XML messages to human-friendly form.
  • Minor bugs fixes.

version 2.4.5 [09 February 2012]

  • Fixed publisher module enabling SSL connections

version 2.4.4 [13 January 2012]

  • In the similar fashion as it was implemented for topic expressions, a new way of specification of message content expressions was provided. E.g.: boolean(//{http://someNamespace}SomeElement[text()="someValue"])

version 2.4.3 [09 January 2012]

  • Implemented an additional, much simpler way of specification of topic expressions in XML. Now the topic expression may be specified fully as a text element using expressions similar to the following one: {http://someNamespace}someTopicExpression

version 2.4.2 [03 January 2012]

  • Modified way of processing MessageContent in notifications: now a notification is not forwarded if MessageContent for a subscription was specified improperly.
  • Added illustrative TopicNamespace to the distribution and modified examples.

version 2.4.1 [30 December 2011]

  • Bugs fixes.

version 2.4.0 [20 December 2011]

  • Migration to gSoap 2.8.5 and QCG-Core 2.4.0.
  • Some improvements and bugs fixes.

version 2.0.0 [April 2011]

  • Reviewed code, minor bugs fixes.
  • Changed the way of starting the service without a database. Now it is impossible to start the service if a database connection is enabled in a config file but the service could not initialize real database connection.

version 1.2.2

  • Minor bugs fixes.

version 1.2.1

  • Fixed proceeding of soap_send_empty_response (requires QCG-Core 2.1.1).

version 1.2.0

  • Implemented notification resending after an unsuccessful send attempt.
  • Modified configuration file.

version 1.1.3

  • Provided interface for listing Subscriptions, Publishers Registrations, PullPoints and TopicNamespaces. Following methods implemented:
    • ListSubscriptions,
    • ListPublishersRegistrations,
    • ListPullPoints,
    • ListTopicNamespaces.

  • Added methods for dynamic adding and removing Topic Namespaces:
    • AddTopicNamespace,
    • RemoveTopicNamespace.

  • Added parameter MaxSendTries to the configuration file. This parameter is going to limit resources utilization. It is associated with a subscription object and limits number of unsuccessful notification send attempts. After exceeded the limit for certain subscription, the subscription is marked as invalid and automatically deleted.

version 1.1.2

  • Migration to QCG-Core 2.1.0 and gSOAP 2.7.16.