[
https://issues.apache.org/jira/browse/EDGENT-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale LaBossiere closed EDGENT-175.
----------------------------------
Resolution: Fixed
Fixed a while ago as IotpDevice.commands() does extract the command data from
the "d" element if it is present.
Furthermore, as noted in the above method, iot-java => 0.2.1 no longer wraps
the command data in a "d" element, nor adds a "ts" element. iot-java
eliminated it because it was apparently an outdated scheme.
> IoT Platform command processing not correctly handling json.
> ------------------------------------------------------------
>
> Key: EDGENT-175
> URL: https://issues.apache.org/jira/browse/EDGENT-175
> Project: Edgent
> Issue Type: Bug
> Components: Connectors
> Reporter: Daniel John Debrunner
> Assignee: Daniel John Debrunner
>
> IotDevice.commands() returns the commands information as a JSON object.
> With Iot Platform (IotfDevice) the key "payload" contains the complete MQTT
> message rather than extracting the command data (the "d" key in the MQTT
> message).
> An IoT Platform message contains two keys, "d" and "ts".
> * "d" is the data for the message
> * "ts" is an optional ISO8601 timestamp
> The intention was that the "payload" key be the payload of the command (not
> the message) for the json format to simplify code for others, and also not
> force every application to have to fetch the "d" key.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
