Hi Akalanka, Thank You Very Much.
------------------------------------- *Shabir Mohamed* *Software Engineer* WSO2 Inc.; http://wso2.com Email: [email protected] <[email protected]> Mobile: +94 77 3516019 | +94 71 6583393 On Fri, Jan 8, 2016 at 4:48 PM, Akalanka Pagoda Arachchi <[email protected] > wrote: > Hi Shabir, > > The behaviour should be similar to other brokers. Hence created the Jira > [1] for this. We will fix this in the latest development version. > > [1] - https://wso2.org/jira/browse/MB-1606 > > Thanks, > Akalanka. > > On Thu, Jan 7, 2016 at 10:46 PM, Shabir Mohamed <[email protected]> wrote: > >> Hi All, >> >> We recently included the MB features into the IoT-Server Pack and >> thenceforth have been trying to get our existing device-communication flow >> to work with the MQTT Queue in the WSO2 MB. >> >> However, we noticed that the communication flow had an issue whilst >> trying to decode the received message from the broker. >> >> *The Scenario is as follows:* >> >> The IoT-Server subscribes to the given broker with wildcard characters; >> thus allowing multiple devices to communicate and send messages to the >> server. >> >> Ex: WSO2IoTServer*/+/*virtual_firealarm*/+* >> >> Ideally what fits into these wildcard spots are the *"device-owner" *and >> the *"device-Id".* >> >> On the other end devices communicating to the server would be publishing >> to the same broker with specific-concrete topics, such as: >> >> WSO2IoTServer*/shabirmean/*virtual_firealarm*/sednjl2094* >> >> When the MQTT-Client at the server end receives any messages matching its >> "wildcard-topic" subscription, a callback is returned with the "MQTT >> Message Received" and the "MQTT Topic" to which the message was sent. >> >> What we do at the IoT-Server's end is that we process-out the "Owner" and >> the "DeviceId" from the topic returned by this callback. This is how we >> have been doing and testing it with other MQTT brokers such as ActiveMQ and >> HiveMQ. >> >> However, with the integration of the WSO2-MB, we notice that the topic >> returned by this callback is *"not"* necessarily the *concrete-topic* to >> which the message was sent to but the *topic to which the subscription >> was made*. >> >> In our case this breaks the flow given that the topic contains wildcard >> characters, hence disallowing us to further continue any of the processing >> that follows. >> >> Can we get some assistance from the MB team as to how we could resolve >> this? >> >> Thanks >> ------------------------------------- >> *Shabir Mohamed* >> *Software Engineer* >> WSO2 Inc.; http://wso2.com >> Email: [email protected] <[email protected]> >> Mobile: +94 77 3516019 | +94 71 6583393 >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Darshana Akalanka Pagoda Arachchi,* > *Software Engineer* > *078-4721791* >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
