Starting from:

$32

Exercise 3.4 solution XML schema:

Exercise 3.4 soltuion XML schema:<?xml version="1.0" encoding="UTF
-8"?
<xsd:schema
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:FI="http://www.travelinfo.com/Flight
Info
"
targetNamespace="http://www.travelinfo.com/Flight
Info
"
<xsd:element name="FlightInfo"
<xsd:complexType
<xsd:sequence
<!-- Mandatory Fields
--
<xsd:element name="DepartureCity" type="xsd:string" minOccurs="1" maxOccurs="1" /
<xsd:element name="ArrivalCity" type="xsd:string" minOccurs="1" maxOccurs="1" /
<xsd:element name="DepartureDate" type="xsd:date" minOccurs="1" maxOccurs="1" /
<xsd:element name="ReturnDate" type="xsd:date" minOccurs="0" maxOccurs="1" /
<xsd:element name="NumberofPassengers" type="integer" minOccurs="1" maxOccurs="1" /
<xsd:element name="Passengers" type="FI:PassengerType" minOccurs="1" maxOccurs="1" /
<!-- Optional Fields
--
<xsd:element name="FlightTime" type="FI:TimeType" minOccurs="0" /
<xsd:element name="ConnectingCity" type="xsd:string" minOccurs="0" /
<xsd:element name="FlightType" minOccurs="0"
<xsd:simpleType
<xsd:restriction base="xsd:string"
<xsd:enumeration value="Nonstop" /
<xsd:enumeration value="1
-stop" /
<xsd:enumeration value="Any" /
</xsd:restriction
</xsd:simpleType
</xsd:element
<xsd:element name="Airline" type="
xsd:string" minOccurs="0" /
<xsd:element name="BookingClass" minOccurs="0"
<xsd:simpleType
<xsd:restriction base="xsd:string"
<xsd:enumeration value="FirstClass" /
<xsd:enumeration value="Business
Class" /
<xsd:enumeration value="EconomyClass" /
<xsd:enumeration value="Any" /
</xsd:restriction
</xsd:simpleType
</xsd:element
</xsd:sequence
</xsd:complexType
</xsd:element
<xsd:complexType name="PassengerType"
<xsd:all
<xsd:element name="Adult" type="xsd:integer" minOccurs="1" maxOccurs="1"/
<xsd:element name="Children" type="xsd:integer" minOccurs="0" maxOccurs="1" /
</xsd:all
</xsd:complexType
<xsd:complexType name="Ti
meType"
<xsd:choice
<xsd:element name="TimeRange"
<xsd:complexType
<xsd:sequence
<xsd:element name="From" type="xsd:time"/
<xsd:element name="To" type="xsd:time" /
</xsd:sequence
</xsd
:complexType
</xsd:element
<xsd:element name="TimeOfDay" type="xsd:time"/
</xsd:choice
</xsd:complexType
</xsd:schemapart
1 Write a simple SOAP program that returns information about commercial flights from the XML Schema of Exercise 3.4(practical part of Problem Set 1).
Here are some of the key elements for implementation.
•Programming Language (e.g., Java, C#, Python)
•IDE (e.g., ColdFusion, .NET, PHP, Microsoft Visual Studio, JAXB, NetBeans, and Eclipse)
•Web Service Protocol: SOAP
•SOAP Implementation: (e.g., Axis)
•Client application (user interface)
•Server application (e.g., Apache Tomcat, IIS) Notes:
This assignment is based on the XML developed from the previous assignment.
part 2
Define a simple Web service in WSDL that returns flight information regarding flights of a particular flight operator, see Exercise 3.4.Instructions: Again this assignment is based on the XML schema you developed for Assignment 1.
In Assignment 1, if the schema you designed does not support the required queries, you will need to make revisions accordingly.
In Assignment 2, if you have implemented the SOAP service using WSDL, you may continue to refine the project and write a brief report. Otherwise you need to implement it using WSDL in this assignment, and include the following components in your submission. You need to show important design decisions you make, key algorithms and data structures you used (if any), and the platform (e.g., software, hardware) based on which the system is implemented. You also need to show screenshots of the execution of your system.
2. A working prototype of the system. You can use any platform or IDE you feel comfortable with as long as you clearly report these details in the project report. Submit the source code along with instructions how to execute your system. Note that the input (queries on the flight availability) and output (response to queries) can be written in any of the following formats: XML file, plain text file, or system I/O. The system can be tested on a live web server, or on a simulated environment such as a local host.

More products