Prompt for the GolfplatzApp

Please create a React-JS application for the GolfplatzModule. The application  has to offer the following views for the user interface: 
    1. GolfclubGolfplatzView 
    2. GolfplatzView 
    3. PlatzbewertungView 
    4. RechtlicheEinschraenkungView 
    5. WasserhindernisView 
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 GolfclubGolfplatzView must contain the following fields: 
    - name: BisJahr   type: LONG 
    - name: Golfclub   type: Golfclub 
    - name: Golfplatz   type: Golfplatz 
    - name: Rolle   type: STRING 
    - name: VonJahr   type: LONG 
The data source for the [Golfplatz] select control should be loaded from the relative URL: 
    "/GolfplatzService/golfplatz"   (HTTP-GET) 
The data source for the [Golfclub] select control should be loaded from the relative URL: 
    "/AbschlagService/golfclub"   (HTTP-GET) 
An existing GolfclubGolfplatz entity should be loaded from the relative URL: 
    "/GolfplatzService/golfclubgolfplatz/{id}"   (HTTP-GET) 
If a new GolfclubGolfplatz entity has been created, the new entity should be posted to the relative URL: 
    "/GolfplatzService/golfclubgolfplatz"   (HTTP-POST) 
If an existing GolfclubGolfplatz entity has been updated, the modified entity should be sent to the relative URL: 
    "/GolfplatzService/golfclubgolfplatz/{id}"   (HTTP-PUT) 
If an existing GolfclubGolfplatz entity has to be deleted, the following relative URL should be called: 
    "/GolfplatzService/golfclubgolfplatz/{id}"   (HTTP-DELETE)

2. The GolfplatzView must contain the following fields: 
    - name: AnzahlLoecher   type: LONG 
    - name: Beschreibung   type: STRING 
    - name: Besitzform   type: STRING 
    - name: Eroeffnungsjahr   type: LONG 
    - name: GesamtPar   type: LONG 
    - name: LaengeMeter   type: LONG 
    - name: Land   type: STRING 
    - name: Name   type: STRING 
    - name: Ort   type: STRING 
    - name: Platztyp   type: STRING 
    - name: Region   type: STRING 
    - name: UmweltHinweise   type: STRING 
    - name: Zugang   type: STRING 
An existing Golfplatz entity should be loaded from the relative URL: 
    "/GolfplatzService/golfplatz/{id}"   (HTTP-GET) 
If a new Golfplatz entity has been created, the new entity should be posted to the relative URL: 
    "/GolfplatzService/golfplatz"   (HTTP-POST) 
If an existing Golfplatz entity has been updated, the modified entity should be sent to the relative URL: 
    "/GolfplatzService/golfplatz/{id}"   (HTTP-PUT) 
If an existing Golfplatz entity has to be deleted, the following relative URL should be called: 
    "/GolfplatzService/golfplatz/{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/golfplatz/{id}" 
Add a HTML table to the view with the following Pflegeaktivitaet columns: 
    - column: Name 
    - column: Frequenz 
    - column: Saison 
    - column: Beschreibung 
    - column: BeeinflusstSpiel 
    - column: Golfplatz 
The table should have the title "Pflegeaktivitaets" und the data must be loaded from the server with the following relative URL: 
    "/TurnierService/pflegeaktivitaet/golfplatz/{id}" 
Add a HTML table to the view with the following GreenkeeperGolfplatz columns: 
    - column: Golfplatz 
    - column: VonDatum 
    - column: BisDatum 
    - column: Greenkeeper 
    - column: Rolle 
The table should have the title "GreenkeeperGolfplatzs" und the data must be loaded from the server with the following relative URL: 
    "/AbschlagService/greenkeepergolfplatz/golfplatz/{id}" 
Add a HTML table to the view with the following Platzbewertung columns: 
    - column: Abschlag 
    - column: Golfplatz 
    - column: Hinweise 
    - column: RatingWert 
    - column: Geschlecht 
    - column: Bewertungsstelle 
    - column: GueltigAb 
    - column: SlopeWert 
The table should have the title "Platzbewertungs" und the data must be loaded from the server with the following relative URL: 
    "/GolfplatzService/platzbewertung/golfplatz/{id}" 
Add a HTML table to the view with the following GolfclubGolfplatz columns: 
    - column: Golfplatz 
    - column: BisJahr 
    - column: VonJahr 
    - column: Golfclub 
    - column: Rolle 
The table should have the title "GolfclubGolfplatzs" und the data must be loaded from the server with the following relative URL: 
    "/GolfplatzService/golfclubgolfplatz/golfplatz/{id}" 
Add a HTML table to the view with the following RechtlicheEinschraenkung columns: 
    - column: VonDatum 
    - column: Golfplatz 
    - column: Behoerde 
    - column: Beschreibung 
    - column: BisDatum 
    - column: Typ 
The table should have the title "RechtlicheEinschraenkungs" und the data must be loaded from the server with the following relative URL: 
    "/GolfplatzService/rechtlicheeinschraenkung/golfplatz/{id}" 
Add a HTML table to the view with the following Umweltbereich columns: 
    - column: Beschreibung 
    - column: FlaecheQm 
    - column: Typ 
    - column: Golfplatz 
    - column: Schutzstatus 
The table should have the title "Umweltbereichs" und the data must be loaded from the server with the following relative URL: 
    "/AbschlagService/umweltbereich/golfplatz/{id}" 
Add a HTML table to the view with the following Infrastruktur columns: 
    - column: Beschreibung 
    - column: Typ 
    - column: Golfplatz 
The table should have the title "Infrastrukturs" und the data must be loaded from the server with the following relative URL: 
    "/TurnierService/infrastruktur/golfplatz/{id}" 
Add a HTML table to the view with the following Loch columns: 
    - column: Beschreibung 
    - column: Par 
    - column: Golfplatz 
    - column: LaengeMeter 
    - column: Vorgabe 
    - column: Nummer 
    - column: Name 
The table should have the title "Lochs" und the data must be loaded from the server with the following relative URL: 
    "/LochService/loch/golfplatz/{id}" 
Add a HTML table to the view with the following Uebungsanlage columns: 
    - column: Typ 
    - column: AnzahlRasenAbschlaege 
    - column: Flutlicht 
    - column: AnzahlUeberdachteAbschlaege 
    - column: AnzahlMatten 
    - column: MaxDistanzMeter 
    - column: Beschreibung 
    - column: Golfplatz 
The table should have the title "Uebungsanlages" und the data must be loaded from the server with the following relative URL: 
    "/LochService/uebungsanlage/golfplatz/{id}"

3. The PlatzbewertungView must contain the following fields: 
    - name: Abschlag   type: Abschlag 
    - name: Bewertungsstelle   type: STRING 
    - name: Geschlecht   type: STRING 
    - name: Golfplatz   type: Golfplatz 
    - name: GueltigAb   type: DATE 
    - name: Hinweise   type: STRING 
    - name: RatingWert   type: STRING 
    - name: SlopeWert   type: LONG 
The data source for the [Golfplatz] select control should be loaded from the relative URL: 
    "/GolfplatzService/golfplatz"   (HTTP-GET) 
The data source for the [Abschlag] select control should be loaded from the relative URL: 
    "/AbschlagService/abschlag"   (HTTP-GET) 
An existing Platzbewertung entity should be loaded from the relative URL: 
    "/GolfplatzService/platzbewertung/{id}"   (HTTP-GET) 
If a new Platzbewertung entity has been created, the new entity should be posted to the relative URL: 
    "/GolfplatzService/platzbewertung"   (HTTP-POST) 
If an existing Platzbewertung entity has been updated, the modified entity should be sent to the relative URL: 
    "/GolfplatzService/platzbewertung/{id}"   (HTTP-PUT) 
If an existing Platzbewertung entity has to be deleted, the following relative URL should be called: 
    "/GolfplatzService/platzbewertung/{id}"   (HTTP-DELETE)

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

5. The WasserhindernisView must contain the following fields: 
    - name: Geschuetzt   type: BOOL 
    - name: Loch   type: Loch 
    - name: PositionBeschreibung   type: STRING 
    - name: Seitlich   type: BOOL 
    - name: Typ   type: STRING 
The data source for the [Loch] select control should be loaded from the relative URL: 
    "/LochService/loch"   (HTTP-GET) 
An existing Wasserhindernis entity should be loaded from the relative URL: 
    "/GolfplatzService/wasserhindernis/{id}"   (HTTP-GET) 
If a new Wasserhindernis entity has been created, the new entity should be posted to the relative URL: 
    "/GolfplatzService/wasserhindernis"   (HTTP-POST) 
If an existing Wasserhindernis entity has been updated, the modified entity should be sent to the relative URL: 
    "/GolfplatzService/wasserhindernis/{id}"   (HTTP-PUT) 
If an existing Wasserhindernis entity has to be deleted, the following relative URL should be called: 
    "/GolfplatzService/wasserhindernis/{id}"   (HTTP-DELETE)