We have found that MMS returns double value in case of LiteralInteger attributes if listing all elements in project ( GET ../elements operation ) but returns the correct value when retrieving only a single element (GET ../elements/{id} operation). This seems to happen only with LiteralInteger in our tests. The issue is reproducible with a project on the public OpenMBEE MMS (see API requests below).
Example
Listing all element from the latest commit of IQS4MMS Demos / TMT / master project:
https://mms.openmbee.org/alfresco/service/projects/PROJECT-0e791c0e-16fe-422f-8f85-462ab035ce99/refs/master/elements contains
Requesting only one of the problematic elements:
https://mms.openmbee.org/alfresco/service/projects/PROJECT-0e791c0e-16fe-422f-8f85-462ab035ce99/refs/master/elements/_18_5_2_e64033a_1510706944742_970575_60595-slot-_18_0_5_c0402fd_1475170761179_993827_168566
We have found that MMS returns double value in case of
LiteralInteger
attributes if listing all elements in project (GET ../elements
operation ) but returns the correct value when retrieving only a single element (GET ../elements/{id}
operation). This seems to happen only withLiteralInteger
in our tests. The issue is reproducible with a project on the public OpenMBEE MMS (see API requests below).Example
Listing all element from the latest commit of
IQS4MMS Demos / TMT / master
project:https://mms.openmbee.org/alfresco/service/projects/PROJECT-0e791c0e-16fe-422f-8f85-462ab035ce99/refs/master/elements
containsRequesting only one of the problematic elements:
https://mms.openmbee.org/alfresco/service/projects/PROJECT-0e791c0e-16fe-422f-8f85-462ab035ce99/refs/master/elements/_18_5_2_e64033a_1510706944742_970575_60595-slot-_18_0_5_c0402fd_1475170761179_993827_168566
Comparing JSON representations of the same element: