Skip to content

CM-278: Improve DataTag address configuration API

Matthias Braeger requested to merge issue-CM-278 into master

The DataTagAddress configuration is not clear and intuitive, in particular for setting the JMS priority and the ValueDeadband type.

The reason for that is that the API allows passing numerics instead of well defined Enums. The reason for this is historical grown code and operational dependencies.

However, the internal logic could be kept and just the user API could be improved.

Expected goal:

  • Introduce Enums for setting JMS message priority and value deadband type for DataTagAddress class
  • Code refactoring to remove usage of old DataTagConstants
  • Overall increase of code robustness
Edited by Matthias Braeger

Merge request reports