Changes

Added a metrics provider handler
(commit: 962b426)

Metrics: Keep track of gauges bound before activation
(commit: 14ac75f)

Added metrics provider presence test
(commit: b5620b5)

Normalize metrics resources names
(commit: 369831b)

Review metrics provider test
(commit: d87aac5)

Enables complex EMF Resource Objects

Signed-off-by: Juergen Albert <j.albert@data-in-motion.biz>
(commit: d25bd7a)

Adds addition Test

Signed-off-by: Juergen Albert <j.albert@data-in-motion.biz>
(commit: e8eaa0b)

Initial version of the programmatic whiteboard
(commit: 4a1d370)

Added WB handler providers property update

Like before, updates of other properties are not supported
(commit: 0037932)

Better Whiteboard handlers priority test
(commit: 1e0e476)

Put constants in an interface and use them internally

Reuse the previous property name for the list of providers
(commit: ed3470c)

Removed generic from WhiteboardHandler interface
(commit: 6bb42da)

Addressed review comments
(commit: ca3e7b4)

Fix to list services and resources on newly created provider instances

... else services when no value was explicitly set are not snapshotted
(commit: 91d5fff)

Added ability to set resource metadata before it gets a value
(commit: 41054e4)

Protect against metadata w/o timestamp
(commit: 2671b7b)

Small enhancements of the provider snapshot API

Added utility methods to easily access services and resources by name
(commit: 6a6a881)

Allow default resource metadata to be set in the model

Provider instances have the ability to independently set metadata values, however in most cases metadata is common to all instances of a model and it is relatively static. It therefore makes sense to be able to define default metadata at the resource model level which is applied to the instance when it is first created.

Note that only the Extra metadata is used to populate the defaults. This prevents other data about the resource (e.g. the resource type and value type) from being added and bloating the metadata. To differentiate default metadata values from metadata values which are set later the default metadata values will have no associated timestamp. This is in line with the behaviour for default resource values.

Signed-off-by: Tim Ward <timothyjward@apache.org>
(commit: fad36b2)

Fixed provider snapshot filterEmptyServices to keep services insertion order
(commit: 202312d)

Allow data and metadata update de-duplication

This commit adds a DuplicateAction to the pushed updates, which determines the behaviour when the pushed update contains a duplicate value or metadata value. A duplicate value is determined by object equality, or == if one value is null. The default for resource values is that duplicates updates are applied, updating the timestamp and generating a update event. The default for metadata values is that duplicate updates are ignored, avoiding timestamp updates and update events. The reason for this difference is that repeated data readings can often give the same value, but this is a new reading. In general metadata values do not change, and so duplicates aren't interesting.

Signed-off-by: Tim Ward <timothyjward@apache.org>
(commit: d56f449)

Further improvements to timestamp mapping
(commit: 508355c)

dataUpdate now supports multiple updates

Signed-off-by: Grégoire Athanase <gregoire.athanase@kentyou.com>
(commit: c7b3cb4)

Annotated DTO mapping error

String fields annotated with @Resource and @Metadata caused all mappings to use the metadata value as the mapping. This should not happen!

Signed-off-by: Tim Ward <timothyjward@apache.org>
(commit: 117c165)