RequstId in OnRoutingStateChanged

Post Reply
ssteiner
Member
Posts: 17
Joined: 05 Feb 2009 09:20

RequstId in OnRoutingStateChanged

Post by ssteiner » 02 Dec 2018 14:41

As per the object model, OnRoutingStateChanged contains a requestId string which is used to correlate requests and responses.

However, the object model of SetRoutesRequest, SetOverflowRoutesrequest and SetForwardRoutesRequest does not contain such a requestId parameter.

So, what's the point of requestId in OnRoutingStateChanged? I hope it's an oversight in the Set* models as this was a very useful thing that I was making use of quite frequently on OTMS.

yblanchard
Member
Posts: 8
Joined: 03 Dec 2018 06:32

Re: RequstId in OnRoutingStateChanged

Post by yblanchard » 03 Dec 2018 10:45

It's a documentation bug(not cleaned from OT): requestId is not supported on O2G. There is no secured mean to make a correlation between the CMIS event received from OXE and a previous request.

==> to be removed from the documentation

ssteiner
Member
Posts: 17
Joined: 05 Feb 2009 09:20

Re: RequstId in OnRoutingStateChanged

Post by ssteiner » 04 Dec 2018 09:21

Snif… would have made my life a LOT easier having that.

ssteiner
Member
Posts: 17
Joined: 05 Feb 2009 09:20

Re: RequstId in OnRoutingStateChanged

Post by ssteiner » 05 Dec 2018 10:32

could it be that this feature is also broken on OTMS? I have a scenario where I could use it, yet, despite sending a requestId for every of my routing request, nothing is ever returned in OnRoutingStateChanged

yblanchard
Member
Posts: 8
Joined: 03 Dec 2018 06:32

Re: RequstId in OnRoutingStateChanged

Post by yblanchard » 06 Dec 2018 04:01

a case should be opened on OTMS to determine if this feature is really broken on OTMS or if it's a local issue

Post Reply

Return to “O2G”