Prompt for the TurnierApp

Please create a React-JS application for the TurnierModule. The application  has to offer the following views for the user interface: 
    1. FairwayView 
    2. GolfplatzTurnierView 
    3. InfrastrukturView 
    4. PflegeaktivitaetView 
    5. TurnierView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 5 views are defined below.

1. The FairwayView must contain the following fields: 
    - name: BreiteMeter   type: LONG 
    - name: GefaelleBeschreibung   type: STRING 
    - name: Grasart   type: STRING 
    - name: HatDogleg   type: BOOL 
    - name: LaengeMeter   type: LONG 
    - name: Loch   type: Loch 
The data source for the [Loch] select control should be loaded from the relative URL: 
    "/LochService/loch"   (HTTP-GET) 
An existing Fairway entity should be loaded from the relative URL: 
    "/TurnierService/fairway/{id}"   (HTTP-GET) 
If a new Fairway entity has been created, the new entity should be posted to the relative URL: 
    "/TurnierService/fairway"   (HTTP-POST) 
If an existing Fairway entity has been updated, the modified entity should be sent to the relative URL: 
    "/TurnierService/fairway/{id}"   (HTTP-PUT) 
If an existing Fairway entity has to be deleted, the following relative URL should be called: 
    "/TurnierService/fairway/{id}"   (HTTP-DELETE)

2. The GolfplatzTurnierView must contain the following fields: 
    - name: ErstesJahr   type: LONG 
    - name: Golfplatz   type: Golfplatz 
    - name: Hinweise   type: STRING 
    - name: LetztesJahr   type: LONG 
    - name: Turnier   type: Turnier 
The data source for the [Golfplatz] select control should be loaded from the relative URL: 
    "/GolfplatzService/golfplatz"   (HTTP-GET) 
The data source for the [Turnier] select control should be loaded from the relative URL: 
    "/TurnierService/turnier"   (HTTP-GET) 
An existing GolfplatzTurnier entity should be loaded from the relative URL: 
    "/TurnierService/golfplatzturnier/{id}"   (HTTP-GET) 
If a new GolfplatzTurnier entity has been created, the new entity should be posted to the relative URL: 
    "/TurnierService/golfplatzturnier"   (HTTP-POST) 
If an existing GolfplatzTurnier entity has been updated, the modified entity should be sent to the relative URL: 
    "/TurnierService/golfplatzturnier/{id}"   (HTTP-PUT) 
If an existing GolfplatzTurnier entity has to be deleted, the following relative URL should be called: 
    "/TurnierService/golfplatzturnier/{id}"   (HTTP-DELETE)

3. The InfrastrukturView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: Golfplatz   type: Golfplatz 
    - name: Typ   type: STRING 
The data source for the [Golfplatz] select control should be loaded from the relative URL: 
    "/GolfplatzService/golfplatz"   (HTTP-GET) 
An existing Infrastruktur entity should be loaded from the relative URL: 
    "/TurnierService/infrastruktur/{id}"   (HTTP-GET) 
If a new Infrastruktur entity has been created, the new entity should be posted to the relative URL: 
    "/TurnierService/infrastruktur"   (HTTP-POST) 
If an existing Infrastruktur entity has been updated, the modified entity should be sent to the relative URL: 
    "/TurnierService/infrastruktur/{id}"   (HTTP-PUT) 
If an existing Infrastruktur entity has to be deleted, the following relative URL should be called: 
    "/TurnierService/infrastruktur/{id}"   (HTTP-DELETE)

4. The PflegeaktivitaetView must contain the following fields: 
    - name: BeeinflusstSpiel   type: BOOL 
    - name: Beschreibung   type: STRING 
    - name: Frequenz   type: STRING 
    - name: Golfplatz   type: Golfplatz 
    - name: Name   type: STRING 
    - name: Saison   type: STRING 
The data source for the [Golfplatz] select control should be loaded from the relative URL: 
    "/GolfplatzService/golfplatz"   (HTTP-GET) 
An existing Pflegeaktivitaet entity should be loaded from the relative URL: 
    "/TurnierService/pflegeaktivitaet/{id}"   (HTTP-GET) 
If a new Pflegeaktivitaet entity has been created, the new entity should be posted to the relative URL: 
    "/TurnierService/pflegeaktivitaet"   (HTTP-POST) 
If an existing Pflegeaktivitaet entity has been updated, the modified entity should be sent to the relative URL: 
    "/TurnierService/pflegeaktivitaet/{id}"   (HTTP-PUT) 
If an existing Pflegeaktivitaet entity has to be deleted, the following relative URL should be called: 
    "/TurnierService/pflegeaktivitaet/{id}"   (HTTP-DELETE)

5. The TurnierView must contain the following fields: 
    - name: Ebene   type: STRING 
    - name: ErstesJahr   type: LONG 
    - name: LetztesJahr   type: LONG 
    - name: Name   type: STRING 
    - name: Tour   type: STRING 
    - name: Wiederkehrend   type: BOOL 
An existing Turnier entity should be loaded from the relative URL: 
    "/TurnierService/turnier/{id}"   (HTTP-GET) 
If a new Turnier entity has been created, the new entity should be posted to the relative URL: 
    "/TurnierService/turnier"   (HTTP-POST) 
If an existing Turnier entity has been updated, the modified entity should be sent to the relative URL: 
    "/TurnierService/turnier/{id}"   (HTTP-PUT) 
If an existing Turnier entity has to be deleted, the following relative URL should be called: 
    "/TurnierService/turnier/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following GolfplatzTurnier columns: 
    - column: Golfplatz 
    - column: LetztesJahr 
    - column: ErstesJahr 
    - column: Turnier 
    - column: Hinweise 
The table should have the title "GolfplatzTurniers" und the data must be loaded from the server with the following relative URL: 
    "/TurnierService/golfplatzturnier/turnier/{id}"