Error handling

[mcarrf90]

Hi guys,

We are currently trying to have a better handling of errors directly in our user interface but we are having some difficulties:

• - When we send, for example, a Transport Point with an error in its intervals, we get back the errorKey 10003 and a message:"Could not plan basic tours (Reason: Could not set transport order). Engine error: Invalid interval (code: -1005) in transport order 1."

• - If we now send two Transports points with error, say transport point with id of 1 with an error of A and a transport point with id of 2 and an error of B, we only get back the exception concerning the first transport order

With this in mind, is there a way where we can get a more verbose or detailed report of these errors? Does the code: -1005 inside the error message mean something? The documentation is not clear at all regarding this issues.

Thanks in advance!

[Bernd Welter]

Hello Martin,

you are right - looks like the other modules documentation contains a section "Error Codes" which seems to be missing in xTour. I asked the developers whether they have at least a PDF or other style document that we can provide through the forum => stay patient!

About the specific error -1005 you mentioned and it's "Invalid interval": looks like the beginning of the interval is after the end of the interval like in this example.

Code: Select all

<ns2:wrappedOpeningIntervals>
      <ns2:Interval from="64800" till="28800"/>
</ns2:wrappedOpeningIntervals>

Furthermore it is relevant that if a LogisticPoint (base class of Depot and TransportPoint) has more than one interval that these intervals have to be provided in ascending order. In the following example both intervals of the depot are valid but they are given in descending order:

Code: Select all

<ns2:wrappedOpeningIntervals>
            <ns2:Interval from="28800" till="64800"/>
            <ns2:Interval from="0" till="10000"/>
</ns2:wrappedOpeningIntervals>

I hope this helps for the moment - if not: get back to us!

Bernd