[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [hono-dev] Redundant(?) properties in API messages
|
On 27/04/16 13:22, Guggemos Dominik (INST/ECS1) wrote:
> Hi, this sounds great, but we can't get it working here.
>
>> Without that change, you could subscribe to telemetry.myTenant and get messages sent to telemetry.myTenant.aDevice, but that would not work if replaceing the '.' with a '/'. However that should soon be addressed.
>
> What we are doing:
> - running the Dispatch Router using the Docker image
> - create a receiver at address: telemetry.myTenant
> - send a message with to property (no target address specified for the sender link): telementry.myTenant.4711
>
> Last thing we see in the trace log is:
>
> ←[36mqdrouter_1 | ←[0mWed Apr 27 11:43:24 2016 MESSAGE (trace) Received Message{to='telemetry.myTenant.4711' body='\a1\0545645'} on link auto-0
>
> But it's not forwarded to the receiver. Should this work out-of-the-box? Or do we miss some further configuration? Maybe you have an idea what we are doing wrong?
I'm very sorry! I was incorrect in my statement. The prefix matching
only works in matching semantics to an address, not in matching a
message address to a receiver. I do apologise for giving out false
information!
