|
public PhysicalAssetWldtEvent(String type) throws EventBusException { |
Use case:
When two physical adapters publish the same property key (e.g., temperature) under different contexts or sources, it becomes impossible for the subscriber to distinguish which property value comes from which adapter. This creates ambiguity in the data and makes it difficult for the subscriber to correctly interpret or route the information.
Example Scenario:
Adapter A and Adapter B both publish a property with the key temperature.
From the subscriber's point of view, both properties appear identical since the key is the same and no clear source or context is provided.
As a result, the subscriber cannot reliably determine which temperature reading belongs to which adapter.
This issue can lead to incorrect data handling, visualization errors, or even faulty decision-making in applications relying on accurate and source-specific information.
Expected Behavior:
There should be a mechanism (e.g., adapter ID) that allows the subscriber to differentiate between properties with the same key coming from different adapters.
wldt-core-java/src/main/java/it/wldt/adapter/physical/event/PhysicalAssetWldtEvent.java
Line 18 in 618652a
Use case:
When two physical adapters publish the same property key (e.g., temperature) under different contexts or sources, it becomes impossible for the subscriber to distinguish which property value comes from which adapter. This creates ambiguity in the data and makes it difficult for the subscriber to correctly interpret or route the information.
Example Scenario:
Adapter A and Adapter B both publish a property with the key temperature.
From the subscriber's point of view, both properties appear identical since the key is the same and no clear source or context is provided.
As a result, the subscriber cannot reliably determine which temperature reading belongs to which adapter.
This issue can lead to incorrect data handling, visualization errors, or even faulty decision-making in applications relying on accurate and source-specific information.
Expected Behavior:
There should be a mechanism (e.g., adapter ID) that allows the subscriber to differentiate between properties with the same key coming from different adapters.