Prompt for the BookingApp

Please create a React-JS application for the BookingModule. The application  has to offer the following views for the user interface: 
    1. BookingView 
    2. BookingSegmentView 
    3. FareClassView 
    4. TicketView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 4 views are defined below.

1. The BookingView must contain the following fields: 
    - name: BookingDate   type: STRING 
    - name: BookingStatus   type: STRING 
    - name: Channel   type: STRING 
    - name: RecordLocator   type: STRING 
    - name: Ticket   type: Ticket 
The data source for the [Ticket] select control should be loaded from the relative URL: 
    "/BookingService/ticket"   (HTTP-GET) 
An existing Booking entity should be loaded from the relative URL: 
    "/BookingService/booking/{id}"   (HTTP-GET) 
If a new Booking entity has been created, the new entity should be posted to the relative URL: 
    "/BookingService/booking"   (HTTP-POST) 
If an existing Booking entity has been updated, the modified entity should be sent to the relative URL: 
    "/BookingService/booking/{id}"   (HTTP-PUT) 
If an existing Booking entity has to be deleted, the following relative URL should be called: 
    "/BookingService/booking/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following BookingSegment columns: 
    - column: SeatNumber 
    - column: Booking 
    - column: FareClass 
    - column: CheckinStatus 
    - column: FlightInstance 
    - column: SegmentStatus 
The table should have the title "BookingSegments" und the data must be loaded from the server with the following relative URL: 
    "/BookingService/bookingsegment/booking/{id}" 
Add a HTML table to the view with the following BookingPassenger columns: 
    - column: Passenger 
    - column: LoyaltyStatus 
    - column: Booking 
    - column: PassengerType 
The table should have the title "BookingPassengers" und the data must be loaded from the server with the following relative URL: 
    "/AirportService/bookingpassenger/booking/{id}"

2. The BookingSegmentView must contain the following fields: 
    - name: Booking   type: Booking 
    - name: CheckinStatus   type: STRING 
    - name: FareClass   type: FareClass 
    - name: FlightInstance   type: FlightInstance 
    - name: SeatNumber   type: STRING 
    - name: SegmentStatus   type: STRING 
The data source for the [FareClass] select control should be loaded from the relative URL: 
    "/BookingService/fareclass"   (HTTP-GET) 
The data source for the [FlightInstance] select control should be loaded from the relative URL: 
    "/FlightInstanceService/flightinstance"   (HTTP-GET) 
The data source for the [Booking] select control should be loaded from the relative URL: 
    "/BookingService/booking"   (HTTP-GET) 
An existing BookingSegment entity should be loaded from the relative URL: 
    "/BookingService/bookingsegment/{id}"   (HTTP-GET) 
If a new BookingSegment entity has been created, the new entity should be posted to the relative URL: 
    "/BookingService/bookingsegment"   (HTTP-POST) 
If an existing BookingSegment entity has been updated, the modified entity should be sent to the relative URL: 
    "/BookingService/bookingsegment/{id}"   (HTTP-PUT) 
If an existing BookingSegment entity has to be deleted, the following relative URL should be called: 
    "/BookingService/bookingsegment/{id}"   (HTTP-DELETE)

3. The FareClassView must contain the following fields: 
    - name: BaggageAllowanceKg   type: LONG 
    - name: CabinClass   type: CabinClass 
    - name: Changeable   type: BOOL 
    - name: Code   type: STRING 
    - name: Refundable   type: BOOL 
The data source for the [CabinClass] select control should be loaded from the relative URL: 
    "/CabinClassService/cabinclass"   (HTTP-GET) 
An existing FareClass entity should be loaded from the relative URL: 
    "/BookingService/fareclass/{id}"   (HTTP-GET) 
If a new FareClass entity has been created, the new entity should be posted to the relative URL: 
    "/BookingService/fareclass"   (HTTP-POST) 
If an existing FareClass entity has been updated, the modified entity should be sent to the relative URL: 
    "/BookingService/fareclass/{id}"   (HTTP-PUT) 
If an existing FareClass entity has to be deleted, the following relative URL should be called: 
    "/BookingService/fareclass/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following BookingSegment columns: 
    - column: SeatNumber 
    - column: Booking 
    - column: FareClass 
    - column: CheckinStatus 
    - column: FlightInstance 
    - column: SegmentStatus 
The table should have the title "BookingSegments" und the data must be loaded from the server with the following relative URL: 
    "/BookingService/bookingsegment/fareclass/{id}"

4. The TicketView must contain the following fields: 
    - name: Airline   type: Airline 
    - name: Currency   type: STRING 
    - name: IssueDate   type: DATE 
    - name: PointOfSaleCountry   type: Country 
    - name: TicketNumber   type: STRING 
    - name: TotalAmount   type: STRING 
The data source for the [Airline] select control should be loaded from the relative URL: 
    "/AirlineService/airline"   (HTTP-GET) 
The data source for the [PointOfSaleCountry] select control should be loaded from the relative URL: 
    "/CountryService/country"   (HTTP-GET) 
An existing Ticket entity should be loaded from the relative URL: 
    "/BookingService/ticket/{id}"   (HTTP-GET) 
If a new Ticket entity has been created, the new entity should be posted to the relative URL: 
    "/BookingService/ticket"   (HTTP-POST) 
If an existing Ticket entity has been updated, the modified entity should be sent to the relative URL: 
    "/BookingService/ticket/{id}"   (HTTP-PUT) 
If an existing Ticket entity has to be deleted, the following relative URL should be called: 
    "/BookingService/ticket/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Booking columns: 
    - column: BookingStatus 
    - column: BookingDate 
    - column: Channel 
    - column: RecordLocator 
    - column: Ticket 
The table should have the title "Bookings" und the data must be loaded from the server with the following relative URL: 
    "/BookingService/booking/ticket/{id}"