XML Schema change – Durations
Line BreakAuthor: Flyball (27 Articles)
Flyball is the Travelfusion mascot and logo – he'll be keeping his eye out for good deals, new technology and travel options and will post the most up to date information on our product development and services, along with new technology and announcements about Travelfusion, our suppliers and clients.
We have fixed a bug in our XML responses where durations are being set to 0 in cases where they cannot be calculated. This has required a change to our XML schemas, since the element needs to be omitted in these cases.
In Router.xsd,
<xs:element name=”Duration” type=”xs:integer” />
is now
<xs:element name=”Duration” type=”xs:integer” minOccurs=”0″ />
This fix is in place on our mirror system, so please test this against your application as soon as possible to ensure no impact. An example of a response is given below. The <Duration> tag is omitted from above <SegmentList>. Please ensure that your application handles this correctly. Cases in which duration tag is omitted are rare and difficult to reproduce.
This change will not go to production for at least 2 weeks, so please let us know within that time if you think it will cause problems for your application.
<Outward>
……
<Price>
<Amount>75.00</Amount>
<Currency>GBP</Currency>
<PriceIncludesTax>true</PriceIncludesTax>
<TaxItemList>
<TaxItem>
<Name>total tax</Name>
<Amount>48.50</Amount>
<Currency>GBP</Currency>
</TaxItem>
</TaxItemList>
</Price>
<SegmentList>
<Segment>
<Origin>
<Type>airport</Type>
<Code>LHR</Code>
</Origin>
<Destination>
<Type>airport</Type>
<Code>CDG</Code>
</Destination>
<DepartDate>30/04/2010-07:25</DepartDate>
<ArriveDate>30/04/2010-09:40</ArriveDate>
<TfOperator>
<Name>British Airways</Name>
<Code>BA1</Code>
</TfOperator>
<TfVendingOperator>
<Name>British Airways</Name>
<Code>BA1</Code>
</TfVendingOperator>
<Operator>
<Name>British Airways</Name>
<Code>BA</Code>
</Operator>
<VendingOperator>
<Name>British Airways</Name>
<Code>BA</Code>
</VendingOperator>
<FlightId>
<Code>BA304</Code>
<Number>304</Number>
</FlightId>
<TravelClass>
<TfClass>Economy With Restrictions</TfClass>
<SupplierClass>E</SupplierClass>
</TravelClass>
<SegmentMayEndWithAStop>false</SegmentMayEndWithAStop>
</Segment>
</SegmentList>
…..
</Outward>
If you enjoyed this post, please consider to leave a comment or subscribe to the feed and get future articles delivered to your feed reader.
